Hello,
thanks for considering.
So far I had no problems using the (anonymous) primary key for the join of
the tables. However, I changed the example so that it worked without the
"anonymous" - attribute, like is is recommended in tutorial 3 ("mapping
classes on multiple joined tables"). The results are the same.
The I tried an "extra foreign key column" in class "NamedPoint" like
desribed in tutorial 3. However, the results are still the same: a fetch
for the parent class only gets parent class objects wihtout any indication
of their true class.
Looks like the "multple joined tables" - solution for inheritance isn't
working porperly.
My problem is: I have a 1:n - relation to the parent class. Navigating
along I get a collection of parent class objects. I have to know which of
these are actually instances of a special child class (there are several
children). Any ideas?
regards,
Birgitta
Armin Waibel wrote:
> Hi,
>
> I never used this feature and don't know much about it, but some things
> may problematic:
>
> test.Point, field-descriptor for PK "id" is declared anonymous
>
> test.NamedPoint, field-descriptor for PK "id" is anonymous
> and no seperate reference field for reference (PK and reference
> id field are the same)
>
> regards,
> Armin
>
> BIRGITTA.MOEHRING wrote:
> >
> >
> >
> >
> > Hello,
> >
> > I am using the ODMG API.
> > i don't know whether this behaviour is to be expected:
> >
> > I am mapping a child class to it's parent class via multiple joined
tables.
> > When I retrive objects of the parent class from the Database, some of
the
> > returned objects should be members of a child class.
> > But if i ask for the objects of the parent class, I only get them as
> > instances of the parent class.
> > In the spy.log - File I can see that only parent objects are retrieved.
> >
> > What can I do to get the "real" objects?
> >
...
