hi robert,
the sql contains the orderby. the problem seems to be the prefetcher. i'll have a look at it.
jakob
Robert S. Sfeir schrieb:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Feb 7, 2005, at 11:52 AM, Jakob Braeuchi wrote:
hi robert,
Robert S. Sfeir schrieb:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Yeah I know, I was avoiding the query customizer didn't want to make it that specific for this particular need, your suggestion of orderby turned out to be the perfect solution. That said, the orderby in the collection-descriptor doesn't order anything if the collection is not sortable.
that's strange. afaik orderby is only handled in the generated sql ?? does ojb at least include 'order by' in the sql ?
Not that I could see in child objects, which is why I think it's affected after the select happens using Collections.sort(...).
R -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCB55mJhqny0eCHK8RAjTMAJ0ddp+xgzh/yYz8Jyk9zcE4S6UJbgCeId3D STOb3QdpeEPrdW2K6k0opzE= =aJ9L -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
