On Aug 21, 2010, at 7:43 PM, Ergo wrote: > yeah a friend suggested to me that it could have been about the fact i > forgot to define innodb in model definitions, and unfortunately that > didnt help anything. > > I guess ill set passive_deletes to True, but it would be still good to > investigate further why this happens - since it seems a reasonable > assumption that the problem would surface with pg drivers too if it > would be something on my side ?
Its very unlikely. We've got dozens of tests for this kind of thing that have passed on all platforms for years - the ORM has no idea if PG or MySQL is in use and does nothing different. A DELETE is just a DELETE on all platforms. MySQL has a lot of quirks, and I'd check that you in fact have InnoDB consistently in use, the same foreign key setup, stuff like that. It also could be some side effect of something upstream with primary keys or something. You'd need to work out an absolute minimum example case to distill out the issue before we'd have something to work with (please note example cases are a single script file, typically with no more than two or three mapped classes, no extraneous columns or imports needed, runs a full mapper setup, inserts sample data, illustrates the failure - fully self contained, succinct, and runnable). -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
