Fix for KeyErrors emanating from TemporaryStorage unexpectedly. A
connection can be holding on to an object with references to an object that has been recently garbage collected. When the object is unghosted in the reference-holding thread, the storage cannot find the oid (because it's out of storage due to gc). We work around this by turning KeyErrors that we believe are due to this scenario into ConflictErrors.
Showing
Please register or sign in to comment