search the archives for my answer to question 1. In short, Castor does the smart thing of holding reference to a resultset inside it's enumerator, so you can load up huge resultsets and you don't instantiate the object till .next() is called. The bad thing is, there was no .size() or .absolute(x) type calls on the queryresults. I added those in a patch that will be handed over "soon" ;)
2. castor doesn't really work in multiple server mode, as far as I know. Has to do with caches. Someone correct me? I think you *might* be able to get something to work, but we haven't had time to check yet. m -----Original Message----- From: Dan Finkelstein [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 29, 2002 12:59 PM To: [EMAIL PROTECTED] Subject: [castor-dev] Beginner Questions.... Hi -- I'm pretty new to this. Could someone quickly answer these questions.... 1. In JDO, if I perform a query like "get every customer", are all the customers returned or is lazy loading used so that the UI can page through the result set? If I have to write extra code to do this, can you describe what is needed. 2. In a scalable environment, with multiple servers running caster, how does the built-in transaction support compare with that in EJB? I'm trying to see under what circumstances castor or EJB might be a better choice. Thanks in advance, Dan ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
