Bug #1999 "SIGNED" is not handled as a reverved word
Submitted: 3 Dec 2003 0:13 Modified: 3 Dec 2003 12:55
Reporter: Masaki Fujimoto Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:4.0.16 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[3 Dec 2003 0:13] Masaki Fujimoto
The manual (2.5.2 Upgrading From Version 3.23 to 4.0) claims that "CHECK, SIGNED, LOCALTIME and LOCALTIMESTAMP are now reserved words", but it seems that "SIGNED" is not yet treated as a keyword.

It's true that "SIGNED" is only used in limited situation (inside CAST fnctions and "table_idnent"), and actually this does not harm at all. so please make this report "not a bug" or "bogus" or somethig like that if this is intentional behavior.

Anyhow, a following example (which is valid for 4.0.16) is odd, isn't it?

How to repeat:
Query OK, 0 rows affected (0.00 sec)
[3 Dec 2003 6:36] Dean Ellis
The Upgrade chapter does mention it, though the Reserved Words chapter of course does not list it, so there is a documentation issue here.

Thank you.
[3 Dec 2003 12:55] Paul DuBois
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant

It's not really reserved. I've updated the documentation
accordingly. Thanks for pointing this out.