Thanks Kevin : ) Adriano Crestani
On 4/27/07, Kevin Williams <[EMAIL PROTECTED]> wrote:
There is no way to morph a 1:m relationship into a M:M relationship. SDO maintains referential integrity. If you have a dept1 with emp1 and then execute: dep2.getEmployees.add(emp1) the graph will automagically remove emp1 from dep1's list of employees and you are left with valid 1:m relationships. --Kevin On 4/27/07, Adriano Crestani <[EMAIL PROTECTED]> wrote: > > As described on > http://wiki.apache.org/ws/ForeignKeyRepresentationAndManagement if a table > EMPLOYEE has a FK to a table DEPARTMENT it's mapped on the sdo graph as > the > DEPARTMENT containing a list of EMPLOYEEs, So it's a 1xN relationship. > However, if the sdo graph, after being created and populated, is modified > and two different DEPARTMENT DataObjects reference the same EMPLOYEE > DataObject the relationship turns to NxN. > > How does the Java DAS handle that? Does it throw an exception? > > Adriano Crestani >
