Re: [Sqlalchemy-tickets] [sqlalchemy] #2721: SQLAlchemy leaks the deferrable keyword in FKs for mys
Brought to you by:
zzzeek
|
From: sqlalchemy <mi...@zz...> - 2013-05-08 01:12:50
|
#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 hour
Resolution: | Keywords: mysql deferrable
Progress State: in queue |
---------------------------+----------------------------------
Changes (by zzzeek):
* status_field: needs questions answered => in queue
Comment:
OK so you are still getting a rough equivalent of "deferrable" with MySQL
here, which was what I was curious about. Since MySQL's foreign keys are
kind of fungible I can see how its fine to skip the keyword on this
platform.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2721#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|