Community
Participate
Working Groups
The implementation uses two fields lastLookupID/lastLookupObject, presumably to optimize lookup performance for repeated lookups of the same object. But the mistaken assumption here is that the ID will continue to refer to the same object; this isn't necessarily the case, as the getObject function may well have been called with a temporary ID, and such an ID may, as a consequence of a commit and subsequent creation of new objects, later designate a different object. See testcase that I'll attach in a minute.
Created attachment 175831 [details] Testcase (as a patch)
Created attachment 175901 [details] Patch including testcase
Created attachment 176080 [details] Patch v2 - ready to be committed Caspar, you can clone this bug to maintenance and commit there without review.
Committed to HEAD
Available in R20110608-1407