A Leg dijo:
> You mean that the ojb iterator work exactly in the same the database
> iterator works, taking in count the caching issues ?
yep.
Antonio Gallardo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
PROTECTED]
Sent: Monday, November 10, 2003 9:17 AM
To: OJB Users List
Subject: Re: Question about getIteratorByQuery
Thomas
Thanks for you answer.
Ok for a simple database call, but when we make this call to the
persistence layer, which bring data step by step does it works ?
I make a request on some
Hi again,
> -Original Message-
> From: A Leg [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 10, 2003 9:17 AM
> To: OJB Users List
> Subject: Re: Question about getIteratorByQuery
>
>
> Thomas
>
> Thanks for you answer.
> Ok for a simple database ca
Thomas
Thanks for you answer.
Ok for a simple database call, but when we make this call to the
persistence layer, which bring data step by step does it works ?
I make a request on some table with 3 enreg numbers 1, 2 and 5
I ask some iterator at the prsistence layer.
And make next.
Somebody cre
Hi Andre,
To follow an index you'll need an order by clause for the indexed
column.
(http://db.apache.org/ojb/api/org/apache/ojb/broker/query/Criteria.html#addOrderBy(java.lang.String,%20boolean))
If you do not use an order by clause the RDBMS is not forced to serve
rows in a certain sequence.
Hi
When we use *getIteratorByQuery and .next().
* do we move throw the table following the index or in some random order ?
If we go in random order, what is the best way (getting advantage of the
cache) to iterate in a table following the index ?
Thank's
Andre
-
