Eclipse Community Forums: EclipseLink » most optimal wy to persisted list?

Help

Home

Home » Eclipse Projects » EclipseLink » most optimal wy to persisted list?

Show: Today's Messages :: Show Polls :: Message Navigator

most optimal wy to persisted list? [message #385744]

Fri, 27 February 2009 08:41

Phillip Ross

Messages: 2
Registered: July 2009

Junior Member

Hi all...

I'm just wondering, for EclipseLink, what is the most optimal way to
persist List fields of an entity. The @BasicCollection does not include
persisting the index of the List elements (as far as I can tell) so when
the EntityManager is cleared or a new one which does not alreayd know
about the in-memory version of the List is used... the index values are
lost. In the current implementation, there are lists being serialized
to byte arrays and stored as LOB columns which is not... optimal :)

Any advice on this? Portability to other JPA providers is of little
concern, if any.

Thanks!
- Phillip

Report message to a moderator

Re: most optimal wy to persisted list? [message #385747 is a reply to message #385744]

Mon, 02 March 2009 14:55

James Sutherland

Messages: 1939
Registered: July 2009
Location: Ottawa, Canada

Senior Member

JPA 2.0 and EclipseLink 2.0 will support ordered lists using an index
column in the database. BasicCollections will also be standardized as
ElementCollection mappings in JPA 2.0. The EclipseLink 2.0 builds already
have this functionality, and some of the functionality was in the 1.1
release.

The drawback with serializing is that you cannot query on the list values.
However, if you don't need to query the values, then there is probably
nothing wrong with serializing the list.

You can also map the list as a OneToMany in JPA 1.0, and define a class
for the value that also contains an index field to order the list by.

---
James
http://www.nabble.com/EclipseLink---Users-f26658.html

James : Wiki : Book : Blog : Twitter

Report message to a moderator

Previous Topic:	ObjectTypeConverter problems
Next Topic:	PersistenceUnitInfo xxx has transactionType JTA, but doesnt have jtaDataSource

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 13:53:43 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter