Would just to say that this has now been cleared up and was not an
SQLAlchemy fault at all.
t o b e
Michael Bayer wrote:
> that shouldnt happen, unless "p" is expired and its row has been
> deleted already. otherwise, you need to send us a test case
> illustrating how youre getting it to do that.
>
> On May 1, 2009, at 12:50 PM, Toby Bradshaw wrote:
>
>
>> Very straightforward, this one.
>>
>> The following:
>>
>> session.delete(p)
>> session.flush()
>>
>> Reliably gets me an ObjectDeletedError exception. p is a known valid
>> object before the delete. No other update, insert or deletes have
>> taken place.
>>
>> Here's the last line of the traceback:
>>
>> File "/usr/lib/python2.4/site-packages/SQLAlchemy-0.5.2-py2.4.egg/
>> sqlalchemy/orm/mapper.py", line 1790, in _load_scalar_attributes
>> raise exc.ObjectDeletedError("Instance '%s' has been deleted." %
>> state_str(state))
>>
>> Known problem or a bug in my understanding ?
>>
>> Thanks in advance.
>>
>> --
>> t o b e
>>
>>
>>
>>
>
>
> >
>
--
t o b e
--
A truly clever developer will create code so easy to understand that a less
than average developer could debug it.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" 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/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
