Hi Markus,
Markus Brigl wrote:
Hi Armin,
it didn't mean the order-by, which does an ordering related to an
attribute. What I mean is the insert order in a list; if an object A
has index 0 in the list I would expect it has the same index after
fetching the list in a different transaction.
At example with Hibernate it is possible to define a column, where the
index of each object is stored; many JDO implementation do this without
any required specification.
Can I reach this target even with OJB?
Sorry, AFAIK this is currently not possible with OJB. Please make a
feature request in JIRA.
regards,
Armin
regards
Markus
On Mon, 2006-03-27 at 11:51 +0200, Armin Waibel wrote:
Hi Markus,
Markus Brigl wrote:
Hi,
I have a problem with the mapping of List's. If I store the list to DB
and reload it the order of the objects are casual and not the same as I
inserted them in the List. Can I configure the repository file in some
way that OBJ stores even the indexes of the List?
Do you mean mapping of 1:n relations? In this case you can specify a
"order-by" element in the collection-descriptor to force ordering.
http://db.apache.org/ojb/docu/guides/repository.html#orderby
regards,
Armin
---------------------------------------------------------------------
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]
