#012108: ezcPersistentStateTransformer::rowToStateArray() relying on definitions with reverse properties set, but it's not automatic

This happens when the definition was Not loaded through fetchDefinition(), which might make this more like an enhancement than a bug as Larson suggested.

Larson suggested as well that protected : ezcPersistentDefinitionManager::setupReversePropertyDefinition() could be made public and that : $ezcPersistentObjectDefinition->__get( 'columns' ) checks if the reverse properties are set up, in order to do it if required, thus preventing the exception.

Larson's suggestion might speed up the code since reverse-properties aren't used when saving an object : there is no-need for them in some cases.

#254897 by James Pic on November 28th, 2007 [Permanent Link]

Discussions on IRC turned out the following: Adding a check to __get( 'columns' ) will add much more overhead than the current implementation has for cases where persistent objects are only stored and not loaded. Therefore this idea will be discarded.

Since ezcPersistentDefinitionManager is the correct place to perform the reverse setup it will be kept there and more documentation on this will be added to the affected classes. In addtion a check for correctly initialized reverse-lookup will be added to ezcPersistentStateTransformer::rowToStateArray() and an exception will be thrown if it is missing.

#255341 by Tobias Schlitt on January 7th, 2008 [Permanent Link]

Fixed in rev. #7096 (stable/PersistentObject/1.3 and trunk).

#255342 by Tobias Schlitt on January 7th, 2008 [Permanent Link]