> In the previous versions of OJB it wasn’t necessary to create reference object
>
> when storing object that has reference but when I try the same thing with OJB
>
> 1.0 RC5 the FK fields are set by OJB to null.
>
> Is creating the reference object
>
> the right thing to do or is there some way to disable this ojb
> functionality?
>>
>> Why this is not the case with OJB 0.9.7!
>> Because I used OJB 0.9.7 for half of year and there were no problems!
ok, I changed this behaviour in CVS head. Now it is possible to store a *new* pc object with populated FK, but without materialized reference. The FK fields are not set to null.
Note: This only works for insert operations (storing of new objects), for update the FK fields will be set to null, when reference object is null.
regards, Armin
Armin Waibel wrote:
Hi again,
I will write some tests for the problem and try to fix it (if possible ;-)) before new release.
regards, Armin
Jurica Viskovic wrote:
Hy Armin
Thank you for replaying so quickly.
About the 'access' attribute in reference-descriptor of Bmg21. That's my
stupidity because I read in some blog that it could help and I forgotten to
move it later on.
Object Bmt05 object exists. So there is no problem there.
Going through the source code of the PersistenceBrokerImpl
I found out that assertFkAssignment and storeReferences methods
are setting my fields to null but I don't know why??
Why this is not the case with OJB 0.9.7! Because I used OJB 0.9.7 for half of year and there were no problems!
If this is the bug is there some way to fix it before the new release!
Thanks,
Jure
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
