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
-------------------------------------------+-------------------------------

Comment (by kashif):

 Actually ATM we're using both mysql and postgres, some environments
 running on mysql and some on postgres. Needed to defer FK checks since
 postgres seems to be more strict and there is no "SET
 FOREIGN_KEY_CHECKS=0;" for postgres. I was loading data into a table
 containing self-referening FKs.

 So when I got everything working with postgres with all tests passing,
 mysql started objecting. For the time being I've worked around that using

     if db.engine.url.drivername.startswith('postgresql'):

 but would be nice if SQLAlchemy could do that :-)

 Thank you for your prompt response. Love SQLA and would love it to be even
 better :-)

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