Re: [Sqlalchemy-tickets] [sqlalchemy] #2721: SQLAlchemy leaks the deferrable keyword in FKs for mysql databases

[sqlalchemy <mi...@zz...>]

#2721: SQLAlchemy leaks the deferrable keyword in FKs for mysql databases
-------------------------------------------+-------------------------------
      Reporter:  kashif                    |      Owner:
          Type:  defect                    |     Status:  new
      Priority:  high                      |  Milestone:  0.8.xx
     Component:  mysql                     |   Severity:  minor - half an
    Resolution:                            |  hour
Progress State:  needs questions answered  |   Keywords:  mysql deferrable
-------------------------------------------+-------------------------------
Changes (by zzzeek):

 * milestone:   => 0.8.xx
 * severity:  no triage selected yet => minor - half an hour
 * status_field:  awaiting triage => needs questions answered


Comment:

 OK, though that's an odd case that you need your FK's to be DEFERRABLE,
 yet your app runs on MySQL (using MyISAM or InnoDB) ?   That's kind of why
 the keyword isn't skipped right now - it assumes if you put "DEFERRABLE",
 you actually need that functionality and if the DB doesn't support it, an
 error should be raised.

-- 
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2721#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python