Hi all,
After migrating our CMS from WO 5.3 to 5.4 we noticed some strange effects on the PrimaryKey generation via EO_PK_TABLE
Our project makes extensive use of horizontal inheritance, using different models in different frameworks.
Normally, there is (and should be) only on row per base entity in EO_PK_TABLE. But this rule was broken, when we try to call anEo.permanentGlobalID() for an unsaved eo. It has the effect, that now in EO_PK_TABLE there is an entry for anEo.entityName(), but the pk value of the base entity was not incremented (which leads to not so amusing effects)
As, of cause, I can't reproduce this behavior with a simple test application, I would like to here if anybody else has experienced this phenomena or hears ringing a bell?
Luckily I can avoid calling permanentGlobalID on unsaved EOs, but not knowing why pk-generation may be broken, doesn't let me sleep to well...
I'm using WO.5.4.2, current Wonder _5_4_branche and using either MySQL or Microsoft SqlServer...
regards,
René Bock
Software Engineering
--
Salient GmbH - the interactive advantage
|