Re: JDO Query Performance

2004-02-09 Thread Gus Heck
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

RE: JDO Query Performance

2004-02-09 Thread Mahler Thomas
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 JDO implementation that will not have

Re: JDO Query Performance

2004-02-09 Thread Gus Heck
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

Re: JDO Query Performance

2004-02-08 Thread Thomas Mahler
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

JDO Query Performance

2004-02-07 Thread Bastian Breithaupt
Hello! I have a table with some 6000 rows and I have to make a query to select some 20 rows. I have read this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg00626.html from the ojb-user list, which says, that first all rows of a tabel are read into memory (in my understanding...) In