Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] JPA 2.0: Ordered Lists open issues

Hi Andrei,

"How do we read back such "damaged' lists into Java app.?
  1. Should we throw an exception?
  2. Try to cure the list by assigning (sometimes randomly) the indexes?
  3. Insert null element into the List that corresponds to missing index (note that then the list size will be greater than the real number of objects)?"
How about eclipselink sensing the corruption of indices and  throwing warning/exception messages to the user about the need to reconstruct indices ? And I would prefer the data retrival working even though warnings are sent to the user about possibility of more entries than returned citing the index corruption.

In that way, eclipselink can provide an API to reconstruct the indices for a given table. I think this process of reconstruction of indices should be asynchronous and run in  background separate from the main thread of eclipse link's execution, as reconstructing indices, for say a 100 GB table, would take a time longer than any one can wait.

On Mon, Feb 9, 2009 at 10:02 PM, Andrei Ilitchev <andrei.ilitchev@xxxxxxxxxx> wrote:
I've added Requirements paragraph to Ordered Lists Wiki page containing Open Issues, please take a look


eclipselink-dev mailing list

Back to the top