Description of problem: The mysql reserved word "binary" is used as a column header in the nova.services table. Version-Release number of selected component (if applicable): essex How reproducible: always Steps to Reproduce: 1. mysql -B -e "use nova; select binary from services;" 2. 3. Actual results: ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'from services' at line 1 Expected results: output of all names of binaries on all cloud nodes. Additional info: See table 5.5.28 on this page for a list of all reserved mysql keywords: http://dev.mysql.com/doc/refman/5.5/en/reserved-words.html
Should be fixed upstream.
I'm sorry I don't understand. Are you saying that the fix is applied upstream or that I should report this problem upstream? Please, please, oh, please, don't make me use launchpad... ;-)
I was saying this issue should be fixed upstream first, and thus reported there. Though perhaps the cost of migrating now isn't worth it? Even custom queries like this can easily be escaped: # mysql -B -e 'use nova; select `binary` from services;'
I'm actually OK with reporting it upstream - but since I discovered the problem in the our preview product, I figured I'd report it to the "vendor" and let you guys work it in upstream.
This does not seem to be something we are willing to propose upstream and does not really seem to cause issues in practice so I am marking it as closed.