On Saturday 11 Feb 2012 10:32:12 AM Michael Bayer wrote: > I ran this and indeed InnoDB appears to be broken here. This is a MySQL > bug. It would appear it is running the cascade between the two "A" rows > and only considering the lead object to be the one deleted. Can't > exactly find it at bugs.mysql.com either, so you'd do everyone a favor if > you could create a ticket over there. I've raised this on lists.mysql. > > SQLAlchemy can try to work around this but for now you can just flip > supports_sane_rowcount off for the whole dialect: Thanks, that would be a lot better than writing a new migrate script. -- Fayaz Yusuf Khan Cloud developer and architect Dexetra SS, Bangalore, India fayaz.yusuf.khan_AT_gmail_DOT_com fayaz_AT_dexetra_DOT_com +91-9746-830-823
signature.asc
Description: This is a digitally signed message part.
