[BlueOnyx:21005] Re: limited length of database names

[Tobias Gablunsky]

This is good news from you again.

Thank you very much,
Tobias

> -----Original Message-----
> From: Blueonyx [mailto:blueonyx-bounces at mail.blueonyx.it] On Behalf Of
> Michael Stauber
> Sent: Thursday, May 04, 2017 7:55 PM
> To: BlueOnyx General Mailing List <blueonyx at mail.blueonyx.it>
> Subject: [BlueOnyx:21004] Re: limited length of database names
> 
> Hi Tobias,
> 
> > another small glitch we found, one thing that the web
> > interface permits to do that is no problem for MySQL
> > or MariaDB respectively. In the process of migrating
> > existing servers onto the BO base we had to create
> > a database with a dot in its name ("wordpress4.1") -
> > no way, is what the web interface tells.
> >
> > A small patch allows us to do it:
> >
> > --- /usr/sausalito/schemas/base/mysql/MYSQL_Vsite.schema.orig	2017-05-
> 03 17:39:37.240714478 +0200
> > +++ /usr/sausalito/schemas/base/mysql/MYSQL_Vsite.schema	2017-05-03
> 17:39:57.485361009 +0200
> > @@ -291,4 +291,4 @@
> >  </class>
> >
> >  <typedef name="mysqlusername" type="re" data="^[A-Za-z0-9][-]{0,4}[A-
> Za-z0-9_%]{1,15}$" />
> > -<typedef name="mysqldatabase" type="re" data="^[A-Za-z0-9][-]{0,8}[A-
> Za-z0-9_%]{1,63}$" />
> > +<typedef name="mysqldatabase" type="re" data="^[A-Za-z0-9][-]{0,8}[A-
> Za-z0-9_%.]{1,63}$" />
> >
> > Again, can you please check that this patch will not introduce any
> harmful things and eventually include it into the system?
> 
> I just checked the updates you suggested into SVN and build a batch of
> RPMs from it for a test box:
> 
> http://devel.blueonyx.it/trac/changeset/2811/
> 
> A dot in the database name created a small problem, though. The GUI
> would create such a database just fine, but it wouldn't delete it.
> 
> If I create a database named "test.with.dots", the database in the MySQL
> directory will be named "test at 002ewith@002edots", while phpMyAdmin shows
> it correctly as "test.with.dots". So far so good. Permissions are also
> set correctly and the MySQL user of the Vsite has access to it just
> fine. So that works well, too.
> 
> When the GUI is used to delete this database, it revokes the rights of
> the Vsite MySQL user from it and the DB disappears from the list of DBs
> that the Vsite owns. But the database itself was still in MySQL as the
> DROP that was run against it didn't go through.
> 
> But that was easy to fix as well:
> 
> http://devel.blueonyx.it/trac/changeset/2812/
> 
> I'm publishing the RPMs now and they should hit the YUM repositories
> within the next 30 minutes.
> 
> Many thanks!
> 
> --
> With best regards
> 
> Michael Stauber
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx