We do run into this error from time to time. In our case, until now it was always a developer error. Here is an example:
Let say you have following classes: Item, ItemStoragePlace, DocumentLineItem.
Primary key of Item: ITEMNO (char)
Primary key of ItemStoragePlace: ITEMNO (char) and STORAGEPLACENO (char)
Primary key of DocumentLineItem: OID (integer)
DocumentLineItem has a one to one relationship to Item (item):
join from: ITEMNO to: ITEM.ITEMNO
and ItemStoragePlace (itemStoragePlace):
join from: ITEMNO to: ITEMSTORAGEPLACE.ITEMNO
join from: STORAGEPLACENO to: ITEMSTORAGEPLACE.STORAGEPLACENO
Note: The same field ITEMNO is used in two relationships.
Lets assume we have following items with primary key ITEMNO: IT01, IT02
Item storage places with primary key ITEMNO, STORAGEPLACENO:
If you create a new DocumentLineItem and set item to IT01, set itemStoragePlace to IT02, ST01, you would get this error.
In our case, we were fortunately able to duplicate the problem in development image. So we were able to track down the issue.
This error in our case occurs if the same field is used in two different joins and if we provide Glorp different values for the same field.
You received this message because you are subscribed to the Google Groups "glorp-group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to glorp-group...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/0805be95-903b-46e3-bb5c-2659e4a36366%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to glorp...@googlegroups.com.