Yes, that could be the reason.
The field in table A can hold a PK of table B, C, or D, but I don't
know, so I have to test each of them.
I thought that I could do a.getB(), then a.getC() then a.getD() until I
get a non-null result.
Wernke
On 2011-07-19 16:45, Andrus Adamchik wrote:
Hi
Hi,
Very often this is caused by DB referential integrity violation in the DB. E.g.
you have a non-NULL FK that has no corresponding PK. Actually we are working on
https://issues.apache.org/jira/browse/CAY-1437 right now that would allow to
have a custom fault resolution strategy, so the case a
Sorry, I forgot to mention this is with Cayenne 3.1M2.
W.
On 2011-07-19 15:16, Wernke zur Borg wrote:
> Hi,
>
> this is similar to https://issues.apache.org/jira/browse/CAY-1379.
>
> I have a to-one relationship from table A to B. When I call b = a.getB()
> I am sometimes getting a non-null resu
Hi,
this is similar to https://issues.apache.org/jira/browse/CAY-1379.
I have a to-one relationship from table A to B. When I call b = a.getB()
I am sometimes getting a non-null result even though a corresponding row
does not exist. I am getting the subject error when I call
b.getSomeAttribute
