On 4/21/15 6:45 AM, Guido Winkelmann wrote:
On Monday 20 April 2015 21:57:40 Oliver Palmer wrote:
[...]
So I got to thinking about what we're doing differently with sqlite and
this bit of code comes to mind:
# sqlite specific configuration for development
if db.engine.name == "sqlite":
@event.listens_for(Engine, "connect")
def set_sqlite_pragma(dbapi_connection, connection_record):
cursor = dbapi_connection.cursor()
cursor.execute("PRAGMA foreign_keys=ON")
cursor.execute("PRAGMA synchronous=OFF")
cursor.execute("PRAGMA journal_mode=MEMORY")
cursor.close()
If I comment the above out in our application.py
<https://github.com/pyfarm/pyfarm-master/blob/f22912cd7d89b93c146801fd1575ff0
6f4883724/pyfarm/master/application.py#L208> module the second nosetests
example above works without issues.
This looks to me like you are "fixing" the problem by just not enabling
foreign key support in sqlite. Since the problem was a foreign key violation,
telling sqlite to not bother enforcing those will make it so we don't see the
problem in the tests anymore, but it doesn't fix whatever is going on here...
what is needed here is actual logging of the tables as they are being
dropped. The claim here is that the ordering of the tables is wrong in
1.0.0. So can we please see the full list of DROP statements logged for
both the 0.9.9 version and the 1.0.0 version? then we will confirm
that, then we look at the table metadata to see that it should in fact
enforce the 0.9.9 ordering, then we've confirmed that's the issue and
can produce a reproduction case.
Guido W.
--
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.
