Christoph wrote:
>Perhaps you could gain a little speed by using OQLQueries instead of
>iterating over the resulting lazy collections if you need only
>specific objects.
Tried that still too slow. This is IMO a fundemental flaw I wish to see addressed ASAP. I tried solving this myself without luck. That is why i ask core contributors to castor where this is on their list of priorities. I raised this issue several months ago and i can not understand why this hasnt gotten more attention. My project is dying on this flaw and if there is no fix within forseeable future I will have to drop castor completely.
>Otherwise refactoring this collection handling part would be definitly
>an improvement ...
It's not only an improvement it is a requirement!! If this doesn't get fixed castor JDO is completely useless for any projects with anything but the simplest class hierachies.
Regards
Jan H. Hansen
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev