hi steve,
i'm happy it solved your problem.
you can define relationships or fields in any class-descriptor, abstract or
concrete. in your case you need it in the abstract because of A pointing to S.
but if you would query for all B or C pointing to a D (ie. D.name) then the
definition in
being passed to the query, as opposed to the column name.
Jakob fixed this in CVS last night.
This May Be A Red Herring.
Cheers,
Charles.
-Original Message-
From: Steve Clark [mailto:[EMAIL PROTECTED]
Sent: 03 March 2004 19:56
To: OJB Users List
Subject: Re: Extent problem with ODMG
I'm
-
From: Steve Clark [mailto:[EMAIL PROTECTED]
Sent: 03 March 2004 19:56
To: OJB Users List
Subject: Re: Extent problem with ODMG
I'm still having this problem, so I'm going to try again.
Using ODMG, RC5, Oracle 9i.
Summary:
- Class A has a 1-to-1 relationship 'abs' to an abstract
this in CVS last night.
This May Be A Red Herring.
Cheers,
Charles.
-Original Message-
From: Steve Clark [mailto:[EMAIL PROTECTED]
Sent: 03 March 2004 19:56
To: OJB Users List
Subject: Re: Extent problem with ODMG
I'm still having this problem, so I'm going to try again.
Using ODMG
I'm still having this problem, so I'm going to try again.
Using ODMG, RC5, Oracle 9i.
Summary:
- Class A has a 1-to-1 relationship 'abs' to an abstract
superclass S
- Class S has concrete subclasses B and C
- Classes B and C share a common relationship 'com' to another
hi steve,
imo OQL is not the problem here.
have you tried to query for AccomplishmentImp, just to see if 'site' can be
resolved ? may be you should use the latest from repository.
jakob
Steve Clark wrote:
I'm having a problem with extents in ODMG. OJB is generating
incorrect (and, in fact,
I'm having a problem with extents in ODMG. OJB is generating
incorrect (and, in fact, invalid) SQL for my OQL query. I'm using
RC5.
My data model consists of Sites, which have collections of each of two
kinds of Accomplishments (SubSites and TechAssists). An Accomplishment
has a collection of
