I have an Interface Substance with multiple extent classes including
ProductSubstance. All the extent classes of Substance extend the
SubstanceBean class and have a super reference to it.
Recently I switched from using a striaght PB query for collections of
Substance interface objects to
I have an Interface I
It has implementing classes A, B, and C
Classes B and C both extend class A and have a super reference to it.
If use the following:
class-descriptor class=I
extent-class class-ref=A /
/class-descriptor
when I search via getCollectionByQuery for instances of I
I am having trouble with the following situation:
Class C extends class B which extends class A
Table A has an auto-incriment PK, id.
Table B also has a field named id that is it's PK and has a FK relationship
to Table A id.
Table C has a PK field named id that has a FK relationship to Table B
I'm attempting to query for all extents of an interface but I don't have a
factory method to create a default instance of my interface.
What I desire to have happen, is for OJB to properly cast each extent into
it's appropriate subclass.
I've found that I can make this happen, but I'm worried
I've noted that when storing an object, the first step done is to store
the 1 to 1 references, then the object itself is stored and then finally,
the 1 to n or m to n references are stored.
Is there a reason for this order of operations?
would it break anything if we stored the 1:1 references
in a DB2 databse
Table A has a PK named id that is also an identity (autoincriment) column
Table B has a PK called id that is also a FK to table A's id field
When attempting to insert Class A, which contains an instance of Class B,
it seems that OJB attempts to insert class B before class A.
This issue looks like it could be the cause of my recent problems as well.
At 03:46 AM 06/17/2004, you wrote:
Hi Denis,
I will try to write a test case for this problem, could please exactly
describe what to do (pseudo code) to reproduce this bug.
regards,
Armin
I have encountered an error that I think may be related to my other
anonymous key issues.
Some of my objects have references with FK values of 0.
I had been using primitives for many of these, but I have gone back and
updated all my key fields to be classes. I think this may have contributed
Armin,
I have tried my code with rc7 and I still have the problem I described.
Looking at the test case you have written, it seems to produce the results
I would like. That is, your code does not return null objects for objects
that should be retrieved via anonymous foreign keys contained
At 06:09 PM 06/09/2004, Armin Waibel wrote:
Hi Brian,
sounds strange, do you use the anonymous keys in a 1:1 or 1:n relation?
Which version do you use? Have you tried latest from CVS?
Can you describe me detailed a test case to reproduce the problem?
I'm using rc6. I have not tried the latest
I have many persistent objects that contain references to other persistent
objects.
I am fairly certain that I have the mapping set up properly, but, the
auto-retrive doesn't seem to cascade down my objects if they use anonymous
keys. That is unless I use proxies; in which case the objects
11 matches
Mail list logo
