Hi,
this is really strange!
The m:n part was refatored after 1.0.1, so if possible try latest from CVS (OJB_1_0_RELEASE branch, the upcoming OJB1.0.2 version, trunk is OJB1.1). This should work, because many test cases with m:n relation pass.
If you think there is a bug in m:n handling (when using the PB-api, odmg problems are known), please send me an test case to show the problem.
regards, Armin
p b wrote:
Hi Armin, I've tried the various configuration with version 1.0.0 and 1.0.1
in Profile you are using auto-retrieve="true" auto-update="true" auto-delete="link" so try the same settings in Organisation.
1.0.0 OK 1.0.1 FAIL --> duplicate key row in object
Or try auto-retrieve="true" auto-update="object" auto-delete="object"
1.0.0 OK 1.0.1 FAIL --> duplicate key row in object
in both collection-descriptor first (most tested settings) and then auto-retrieve="true" auto-update="object" auto-delete="link"
1.0.0 OK 1.0.1 FAIL --> duplicate key row in object
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
