E&S CVS Commit: PEAK - Fixed a couple of persistence issues: if a transaction hadn't been joined

[pje at eby-sarna.com]

Module Name:	PEAK
Committed By:	pje
Date:		Tue Dec 17 22:35:47 UTC 2002

Modified Files:
	PEAK/src/peak/storage: data_managers.py

Log Message:
Fixed a couple of persistence issues: if a transaction hadn't been joined
when modifying a persistent object, the object would be added to its DM's
'dirty' set before the error occurred.  Also, aborting a transaction didn't
actually rollback the in-memory state of modified persistent objects,
because '_p_deactivate()' is a no-op for modified objects.  You have to
'del ob._p_changed' first.  Anyway, this shows how minimal the peak.storage
test suite is at present.  I should probably add some tests to cover these
and related issues.


To view diffs of this commit, you can use the following URL(s):
http://cvs.eby-sarna.com/PEAK/src/peak/storage/data_managers.py.diff?r1=1.9&r2=1.10

To generate a diff of this commit:
cvs rdiff -r1.9 -r1.10 PEAK/src/peak/storage/data_managers.py

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.