| Bug #5292 | show create table: backquotes present in constraint w/ SQL_QUOTE_SHOW_CREATE=0 | ||
|---|---|---|---|
| Submitted: | 30 Aug 2004 13:00 | Modified: | 30 Oct 2004 8:55 |
| Reporter: | Alex Woick | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 4.1.3-beta | OS: | Linux (Linux) |
| Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
[24 Sep 2004 11:55]
Marko Mäkelä
ChangeSet@1.2027, 2004-09-24 14:29:01+03:00, marko@hundin Also, the identifiers in foreign key constraints were printed within backticks, regardless of SET SQL_MODE=ANSI. I fixed that as well. The fix should be approved in the beginning of next week, and it should be included in MySQL 4.1.6.
[30 Oct 2004 8:55]
Heikki Tuuri
Fixed in 4.0.6.

Description: "show create table" returns backquotes in the constraint statements, even if SET SQL_QUOTE_SHOW_CREATE=0. How to repeat: execute: SET SQL_QUOTE_SHOW_CREATE = 0; SHOW CREATE TABLE table_with_constraints; Example table output: mysql> SHOW CREATE TABLE log_file\G *************************** 1. row *************************** Table: log_file Create Table: CREATE TABLE log_file ( id_log_file int(11) NOT NULL auto_increment, id_log_instance int(11) default NULL, id_cf_filetype int(11) default NULL, filename varchar(255) collate latin1_german1_ci NOT NULL default '' COMMENT 'name of the file', filesize int(11) NOT NULL default '0' COMMENT 'size of the file', filetime datetime NOT NULL default '0000-00-00 00:00:00' COMMENT 'timestamp of the file', contents mediumtext collate latin1_german1_ci NOT NULL COMMENT 'contents of the file', PRIMARY KEY (id_log_file), KEY idx_id_log_instance (id_log_instance), CONSTRAINT `log_file_ibfk_1` FOREIGN KEY (`id_log_instance`) REFERENCES `log_instance` (`id_log_instance`) ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_german1_ci COMMENT='attached complete file from analysis' 1 row in set (0.01 sec)