On 4/26/07, Ovid <[EMAIL PROTECTED]> wrote: >> Unfortunately, in your example, that will fail (I think) because a column in >> the left-hand side of the column_map in the suspended relationship is part of >> the primary key of the server class. I'll try to add a fix for this soon. >> Any strong feelings about how it *should* behave? >> > Yup. Same behavior. Darn. I can work around this with a 'one to many' > relationship, but that's more pain than it's worth. I'm just going to delete > the relationship and code everything by hand. > > And I can't say I have strong feelings about how this should behave. 'one to > optional one' should just allow me to set up an 'optional' second class to be > associated with the primary class and delete the second class, as needed. > e.g., if 'A' has an optional 'B', the existence or non-existence of 'B' should > have no material affect on 'A'.
Okay, this is fixed in SVN. Now the key columns are only set to undef if the "referential_integrity" (for fks) or "required" (for relationships) attribute is true. And even when the key columns are set to undef, if a column is also part of a primary key, it is not set to undef. -John ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
