Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] Minutes: Functional Discussion - Ordered Lists

But we can really only support nulls for join table relationships.  We couldn't do it for target table relationships.  For target table relationships there would be no distinction between nulls and corruption.

Having one mapping respond one way to nulls and the others respond differently would create ambiguity for our users.  We would have to clearly document what was supported and what wasn't and this would add complexity to the development.

Are there known users who need this functionality?

Michael Keith wrote:
My point was that it should be valid for users to have nulls. Corruption issues are secondary to functionality, I think, and should be solved around that.
-----Original Message-----
From: Gordon Yorke
Sent: Tuesday, March 10, 2009 8:25 AM
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Minutes: Functional Discussion - Ordered Lists

But then users would have to code checking for nulls during iteration for a case that should never happen.  Most users would not expect this requirement and would not code for it resulting in unrecoverable exceptions on read.
Better for us to ignore the corruption on read and fix the indexes on write.  Raising warnings if we do discover corruption.

Michael Keith wrote:
That's what I would expect. 
-----Original Message-----Andrei Ilitchev Monday, March 09, 2009 5:03 PMDev mailing list for Eclipse Persistence ServicesRe: [eclipselink-dev] Minutes: Functional Discussion Orderedyou saying that two rows in the db with order values 0 2 should be as a list of 3 elements with null in the middle?Original Message ----- "Michael Keith" <MICHAEL.KEITH@xxxxxxxxxx>"Dev mailing list for Eclipse Persistence Services" <eclipselink-dev@xxxxxxxxxxx>Monday, March 09, 2009 4:31 PMRE: [eclipselink-dev] Minutes: Functional Discussion Ordered couldn't be at the that I wanted to mention is the null value case.example:l = new ArrayList();null);the order of obj1 to be 0 abd obj3 to be the list would be (obj1, null, obj3).comments below...   
-----Original Message-----Peter KroghMonday, March 09, 2009 2:45 PMeclipselink-dev@xxxxxxxxxxx[eclipselink-dev] Minutes: Functional Discussion - OrderedIssues:Non Contiguous Index valuesResolution: include the expected index in the where clause.  If thefails, assume that the list is non-contiguous.the list.     
Could it also be a list manipulation collision and be theof an optimistic lock exception? Indexing new elements in un-instantiated IndirectListsResolution: Don't support un-instantiated IndirectLists withList.OrderColumn tableResolution: One to Many: support OrderColumn on any Target table Join Table: only support OrderColumn on Join Table Throw an exception if any other table is specified.     
Okay. Duplicate supportResolution: Looking into Duplicates now. Will determine impact of supporting Duplicates as furtheris done. Duplicates with Private Owned an issue.     
Spec does not enumerate the duplicates issue. "Two-way" order supportEmployee.projects and Projects.employees; say add ORDER_EMPORDER_PROJ fields to the join table?Resolution: We are not at this time supporting a different ordering onmappings sharing the same join table (one being read only).     
Spec is silent on having ordered Lists on both sides of an worth mentioning in the spec, though. Constraints in the DB - is that possible?Resolution: Log a Doc Bug: can't make index column part of the PK.Target optimistic lockingResolution: Only uni-directional, use the flags that already exist onMapping. Move the flags to OneToMany.Message-----Peter KroghMonday, March 09, 2009 9:11 AMeclipselink-dev@xxxxxxxxxxxRE: Functional Discussion - Ordered Listswill use the call in information described here: KroghThursday, March 05, 2009 3:39 PMeclipselink-dev@xxxxxxxxxxxFunctional Discussion - Ordered Listspropose that we have a dicussion on the functionalof Ordered Lists.doc with open issues is here: 
Monday: Mar 9th 2009 1:00pm estDoug Clarke, Shaun Smith, Andrei Ilitchev, GordonMike KeithKroghmailing listeclipselink-dev@xxxxxxxxxxx   
_______________________________________________mailing listeclipselink-dev@xxxxxxxxxxx listeclipselink-dev@xxxxxxxxxxx listeclipselink-dev@xxxxxxxxxxx 

_______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx

Back to the top