Thanks for your answer.
Let me try to explain what we want to do:
This is what we want to achieve:
All tables are in a cascaded 1:n model.
Now, can I somehow ensure that the tables are stored in this order:
(*) The reason is, we have a trigger on the database that should only
execute when all objects are stored.
Another way to put this question: can we make any asumptions on the
sequence of the <class-descriptor> tag in the repository file ?
If the table sub_tb_2 is indeed the last <class-descriptor> in the
repository file, can we then assume the store operation actually works as
we intend ?
> Dear List,
> Is there any way the influence the sequence that nested objects gets
> in ?
No, OJB always store all 1:1 references of the main object first, then
the main objects was stored and after that all 1:n and m:n references
If you need to store e.g. a collection object first try something like this
this first insert the refObject without FK settings, then the refObject
was added to the mainObject and the FK in refObject are set when the
mainObject was stored.
> We have a processing that requires the store to be done in a specific
> Any hints or references would be greatly appreciated.
> Thanks for your help
This e-mail, including attachments, is intended for the person(s) or
company named and may contain confidential and/or legally privileged
information. Unauthorized disclosure, copying or use of this information
may be unlawful and is prohibited. If you are not the intended recipient,
please delete this message and notify the sender
To unsubscribe, e-mail: ojb-user-unsubscribe@xxxxxxxxxxxxx
For additional commands, e-mail: ojb-user-help@xxxxxxxxxxxxx