In certain situations, MiddleKit could store an invalid object
reference in the SQL database. This would cause a warning when
retrieving the object and a disconnect between the source and target
This was first reported by Dave Rogers who ran into it when A points to
B and B points to A.
Stephan Karlsson reported it for when A points to
B, both are new objects, and A is archived first.
I have fixed the bug and added a test case for this. All existing test
If you are using MiddleKit, please get the latest CVS version and try
MiddleKit does some funky code generation in GeneratedPy/GenFoo.py to
import the super class that resides in the above directory. Previously,
this code used ".." in sys.path, which was flat out wrong because that
relates to your current working directory. The new version works off of
__file__, which should be correct.
The test suites pass and my projects work, but the change is somewhat
If you use MiddleKit, please consider a cvs update, re-generation and
then trying things out.
If you are using MiddleKit, please update to the latest cvs.
A new test case in the test suite covers the (old) bug and all
pre-existing test cases pass.
I fixed an obscure bug involving _inherited_ obj refs when they have to
be UPDATEd post-INSERT of the containing object. A rare case that I
first encountered tonight.
Explaining the full details would be tedious and boring. If you really
want to know, see the latest checkins and study SQLObjectStore as well
as the new Tests/MKObjRef.mkmodel/TestEmpty3.py.