Hi all,
does anybody know if there exist a config var in PMA that define the style of generated tablenames ? Is there a rule for programmers ?
When I edit the structure of a field, PMA produces only "tablename" as table name. When I insert data it produces "dbname" . "tablename".
Example:
ALTER TABLE `table1` CHANGE `field3` `field3` INT( 14 ) NOT NULL ;
INSERT INTO `test`.`table1` ( `field1` , `field2` , `field3` ) VALUES ( '1', '2', '3' );
Thank you
Alex
Alexander Rutkowski a écrit :
Hi all,
does anybody know if there exist a config var in PMA that define the style of generated tablenames ? Is there a rule for programmers ?
When I edit the structure of a field, PMA produces only "tablename" as table name. When I insert data it produces "dbname" . "tablename".
Example:
ALTER TABLE `table1` CHANGE `field3` `field3` INT( 14 ) NOT NULL ;
INSERT INTO `test`.`table1` ( `field1` , `field2` , `field3` ) VALUES ( '1', '2', '3' );
Thank you
Alex
It's more a programming style where the author of a specific module included the db name or not.
On 22.07.2009 17:09, Alexander Rutkowski wrote:
Hi all,
does anybody know if there exist a config var in PMA that define the style of generated tablenames ? Is there a rule for programmers ?
When I edit the structure of a field, PMA produces only "tablename" as table name. When I insert data it produces "dbname" . "tablename".
including the database name is a more safe approach, query will work regardless of currently selected database
otherwise you have to ensure correct database is selected
i would always prefer including database name
Sebastian Mendel schrieb:
i would always prefer including database name
Ok, I see - there is no global setting. I asked because I has to cut off the `dbname`. prefix from the tablename for my tracking report SQL dump. Otherwise the export to the temporary database (or to any other database) will produce error messages.