This is a problem in MySQL 4.1.x only, which is alpha at the moment, while it doesn't seem to be a problem in MySQL 4.0.x, currently in production.
This can be fixed changing the field name as suggested by Ax, or using double quotes.
I lower the priority and wait for some feedback on the best way to fix (renaming or double quotes)
Double quotes is ANSI, but works in MySQL only in ANSI Mode. In standard mode you must use backticks, which is not ANSI.
So it seems table renaming is the only portable solution.
Comments
Comment #1
marco commentedThis is a problem in MySQL 4.1.x only, which is alpha at the moment, while it doesn't seem to be a problem in MySQL 4.0.x, currently in production.
This can be fixed changing the field name as suggested by Ax, or using double quotes.
I lower the priority and wait for some feedback on the best way to fix (renaming or double quotes)
Comment #2
dries commentedI assume that using double quotes is a MySQL-ism and not ANSI SQL?
Comment #3
marco commentedDouble quotes is ANSI, but works in MySQL only in ANSI Mode. In standard mode you must use backticks, which is not ANSI.
So it seems table renaming is the only portable solution.
Comment #4
moshe weitzman commentedfixed with a table rename. now in CVS. thanks marco
Comment #5
(not verified) commentedComment #6
marco commentedit has not been committed yet, I re-open
Comment #7
al commentedI think this has been fixed:
al@drupal:~/drupal/drupal> grep types database/database.mysql
Can someone please confirm and CLOSE this?
Comment #8
killes@www.drop.org commentedConfirmed, did not find "types" in sql-statement in core.