Skip to main content

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


Open Issues: Non Contiguous Index values 
  include the expected index in the where clause.  If the update fails, assume that the list is non-contiguous.  Re-index the list. Indexing new elements in un-instantiated IndirectLists 
 Resolution: Don't support un-instantiated IndirectLists with Ordered List. OrderColumn table 
  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. Duplicate support 
  Looking into Duplicates now.
  Will determine impact of supporting Duplicates as further prototyping is done.
  Duplicates with Private Owned an issue. "Two-way" order support 
 Employee.projects and Projects.employees; say add ORDER_EMP and ORDER_PROJ fields to the join table? 
  We are not at this time supporting a different ordering on 2 mappings sharing the same join table (one being read only). Constraints in the DB - is that possible? 
  Log a Doc Bug: can't make index column part of the PK. Target optimistic locking
  Only uni-directional, use the flags that already exist on the Mapping.
  Move the flags to OneToMany.

-----Original Message-----
From: Peter Krogh 
Sent: Monday, March 09, 2009 9:11 AM
To: eclipselink-dev@xxxxxxxxxxx
Subject: RE: Functional Discussion - Ordered Lists

We will use the call in information described here:

-----Original Message-----
From: Peter Krogh 
Sent: Thursday, March 05, 2009 3:39 PM
To: eclipselink-dev@xxxxxxxxxxx
Subject: Functional Discussion - Ordered Lists

I propose that we have a dicussion on the functional direction of Ordered Lists.

A doc with open issues is here:

Monday: Mar 9th 2009
Time:  1:00pm est
Required: Doug Clarke, Shaun Smith, Andrei Ilitchev, Gordon Yorke, Mike Keith

Peter Krogh

Back to the top