Hi again Gus,
> >
> Cool. I'll peek at it some time, like maybe tonight or next
> weekend
great!
> 1 and 3 look interesting. I know nothing about bytecode
> however... What
> about an xdoclet based source code enhancer as an additional option?
sounds OK! But at some point in time we w
SO all you can do for the moment is to wait for our own full JDO
implementation that will not have such limitations.
So when does this start?
In fact it has already started. Have a look at the folder
src/java/org/apache/ojb/jdo in the source distribution.
This new implementation is
Hi Gus,
> -Original Message-
> From: Gus Heck [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 09, 2004 4:42 PM
> To: OJB Users List
> Subject: Re: JDO Query Performance
>
>
>
> >
> > SO all you can do for the moment is to wait for our own full J
SO all you can do for the moment is to wait for our own full JDO
implementation that will not have such limitations.
So when does this start? Will it use the current JDO related classes or
rewrite them? I might be interested in pitching in, a bit when it does
if I can find a small chunk or two
Hi Bastian,
Your understanding of that other message is correct.
As the JDORI plugin mechanism does not provide any abstraction of
performing selections.
This is a deficit of SUN's JDORI and not of OJB!
The bad news is that there is no way to get around this problem.
SO all you can do for the mo