Menu
▾
▴
#1098 (ok 4.0) small improvement in generated SQL
fixed
1
2013-06-11
2008-07-03
No
Hello,
creating a new database and copying in parallel the SQL statements into an install script I realized, that the "CREATE TABLE" statement isn't ended with a semicolon and the "CREATE DATABASE" statement has a leading space character before the last semicolon.
Logged In: YES
user_id=1358563
Originator: YES
Furthermore for the displayed "GRANT SELECT , INSERT ON `zert` . * TO" statement the spaces between the database name and the asterix makes problems at my system.
Logged In: YES
user_id=1358563
Originator: YES
BTW an "ALTER TABLE" statement doesn't prefix the table name with the schema as it is done for other SQL commands.
Logged In: YES
user_id=1383652
Originator: NO
>the spaces between the database name and the asterix makes problems at my system.
very old bug, click edit as a workaround ....
Logged In: YES
user_id=1358563
Originator: YES
>very old bug, click edit as a workaround ....
h, please don't misunderstand me - phpmyadmin did what I want - but IMHO it would be better, if the commands were formatted always in the same way - especially if you copy + paste them into an external script for later use.
For 3.1.2, semicolon added to CREATE TABLE.
Todo: ALTER TABLE (many places to modify).
Further fixes needed in the syntax highlight logic.
This requested feature was implemented in the repository and will be part of a future release; thanks for suggesting.