what do you mean "delete", like, objectstore.delete(obj) ? if so,
thats not hard at all, since nothing actually happened to your object
except that it was put into a list.
if you mean like, you totally dereferenced the object, it was never
marked as "new", and it was never saved in the database, then no, its
not holding onto that.
the "roll back the attributes" thing, ehhh, even though the
attributes package has it, i dont know how much I want to get into
that, for reasons like this; its not saving a whole in-memory
snapshot of everything, its just saving the changes to scalar and
list attributes on objects. at the end of the day its not a total
"rollback all the in-memory changes" solution and I can see it just
being a let-down more often than not.
of course, the real way to "roll back" is just to wipe everything
clean and re-load from the database (although that still is not going
to resurrect a deleted object that was never saved...).
On Feb 6, 2006, at 12:02 AM, Shuo Yang wrote:
Hi Guys:
This was documented under UOW section:
" - The ability to "roll back" the attributes that have changed on
an object instance since the last commit() operation. this is also
handled by the attributes package."
I am guessing that if I deleted some objects within a UOW, that
this could not be rolled back? Are there other ways to achieve
such effect?
Thanks,
--
----------------------------------------------------------------------
-----------------------------
John S. Yang
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
