Bug #25168 "Incorrect table name" instead of "Identifier too long" if table name > 64 chara
| Submitted: | 19 Dec 2006 9:33 | Modified: | 5 Jun 2012 16:17 |
|---|---|---|---|
| Reporter: | Heinz Schweitzer (Gold Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: DDL | Severity: | S3 (Non-critical) |
| Version: | 4.1/5.0/5.1 | OS: | Windows (XP/Linux) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | qc | ||
[19 Dec 2006 9:33]
Heinz Schweitzer
[19 Dec 2006 12:54]
MySQL Verification Team
Thank you for the bug report. This isn't Administrator bug it display
the error message send by the server:
C:\dbs\5.0\bin>mysql -uroot -P3307 test
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.27-community-nt-log
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> create table t01234567890123456789012345678901234567890123456789012345678901234567890123456789(id serial)
-> ;
ERROR 1103 (42000): Incorrect table name 't01234567890123456789012345678901234567890123456789012345678901234567890123456789'
mysql> create table t01234567890123456789012345678901234567890123456(id serial);
Query OK, 0 rows affected (0.48 sec)
I changed category.
[5 Jun 2012 16:17]
Paul DuBois
Noted in 5.6.6 changelog. For table or database names that are longer than 64 characters, the error "Incorrect table name" was returned rather than "Identifier too long".
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.060 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.