Finally, note that I'm _not_ asking for sqlalchemy to maintain the
collections for me. All I'm asking is for the cascade code not to
attempt to delete objects that have already been deleted and flushed,
or at least to safely handle the exception it raises when it does.
OK, what
On Jan 30, 12:51 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Jan 30, 2:35 pm, Ian Kelly [EMAIL PROTECTED] wrote:
Finally, note that I'm _not_ asking for sqlalchemy to maintain the
collections for me. All I'm asking is for the cascade code not to
attempt to delete objects that
On Jan 30, 2007, at 5:26 PM, Ian wrote:
the changed state on your objects is stored in an attribute on the
object itself called _state (and actually, its not the changes as
much as what was loaded from the database). you can freely move
instances from one session to the next (using either
On Jan 29, 8:19 pm, Ian Kelly [EMAIL PROTECTED] wrote:
I can live with this response, but I still consider it a bug. If I
have to manually remove the instances whenever I delete an object
where this exception is possible, then I might as well just be doing
the entire cascade for the
