Hi everyone, I am testing sqlalchemy-migrate coupled with sclalchemy. My table has constraint with uppercase name like FK_1_1 . Alchemy-migrate sees the name and thinks it should be in ticks :) then it passes the "ticked" name to sqlalchemy and the latter again sees that fk needs to be quoted .. at the end sql fails because the name becomes ```FK_1_1```
Shouldn't sqlalchemy/sql/compiler.py check if a name already is in ticks before quoting it again? I am on centos/oracle 6.5 with alchemy 0.7.8, though looking thru the newer source code I got the same impression about quoting :) Many thanks in advance! Vladislav -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
