Hello Gaetan,
Sorry, maybe I was not clear enough : The solution that was proposed
(passive_deletes) works for me, I only mentioned in my previous post that I had
problems defining foreign key constraints in elixir (because I didn't know I
had to put a passive_deletes as an argument, I thought a ondelete="RESTRICT"
was enough.), but then a solution (passive_deletes) was given, that was not
obvious for me to see.
Your scripts show that sqlalchemy, too, needs passive_deletes to be passed to
the backref for the fk constraints to be fired, which I wasn't aware of until
know. I grepped for passive_deletes in the legacy models code base with no
results, but still, the original developer told me that the exceptions were
fired but ...
>Sorry, but I do *not* believe you, and I will not until you show me an
>example of plain SQLAlchemy code that does not exhibit the same behavior
>that you are blaming on Elixir.
*snap* ! this is exactly what I should have told the original developer
responsible of the legacy code.
And no, I don't (and didn't) blame elixir for anything. You know the adage :
"Computers don't have problems, they have users". Maybe a
s/Computers/Libraries/ and s/users/coders who (don't know how to) use it/
substitution would fit here.
Y.Chaouche
--
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.
