Re: [Sqlalchemy-tickets] [sqlalchemy] #2841: MySQL doesn't support MATCH, INITIALLY, or DEFERRED

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

#2841: MySQL doesn't support MATCH, INITIALLY, or DEFERRED
---------------------------+----------------------------------
      Reporter:  uijllji   |      Owner:  zzzeek
          Type:  defect    |     Status:  new
      Priority:  high      |  Milestone:  0.8.xx
     Component:  mysql     |   Severity:  minor - half an hour
    Resolution:            |   Keywords:  mysql, ddl, schema
Progress State:  in queue  |
---------------------------+----------------------------------

Comment (by zzzeek):

 well yeah, this is a total crapshow.   we have a precedent of ignoring
 "deferrable" already set up in #2721.  But the approach in #2721 is really
 only valid when someone is using SET FOREIGN_KEY_CHECKS=0.

 So i think we need to rethink this entirely.   I'd like to invalidate
 #2721 and give that user an entirely different path for his FK situation.
 DEFERRABLE and INITIALLY will be let through again, causing MySQL to fail
 (it fails, I checked).  MATCH will totally raise an error.   in 0.8,
 nothing changes but everything warns.

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