> > When I did not have them set, > > I got an error while making inserts. It seemed like Elixir do not pay > > attention on the order of insertions (it wants to insert values into > > the relation-binding table before it inserted the reffered values > > itself). > > Strange. That shouldn't be the case. If it is, it's either you are > doing something weird or it's a bug (possibly in SQLAlchemy). Could > you send a self-contained (and as small as possible) test case?
OK. I double-checked what I was doing and I must agree that it was my fault. I have to confess that I was doing manual inserts to the m2m table before I did an insert to one of the parent tables and that's why I run into this problem. So it is definately not Elixir's nor Sqlalchemy's problem. I simply started to look for a way to enable "late" constraint checks and define them just like it is possible in the ManyToOne relation. I didn't even thought of just changing the order of the inserts, so that m2m table gets filled in as the last one. Sorry for the confusion. Still it would be nice to have a possibility of defining these parameters also in ManyToMany relation. Best regards, Lukasz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
