I'd side with Simon on this. If you're really importing a ton of
records, consider using raw JDBC. batched prepared statements are
your friend!
Unfortunately, you may end up rewriting some custom logic from your
EO classes. You can get some pretty impressive speeds with this
technique, though, and it will almost certainly solve your memory
issue (break the batch updates up if needed).
On Sep 26, 2007, at 3:15 AM, Shravan Kumar.M wrote:
No! its Oracle 9i.
<effigent_logo.jpg>
Thank you,
Shravan Kumar.M
Effigent India
www.effigent.com
-----------------------------------------------------
On 26-Sep-07, at 3:43 PM, Andrew Lindesay wrote:
Hello Shravan;
We recently had a problem of not able to upload a file having 40K
number of records from our WebObjects application to the
database. We used to get java.lang.OutOfMemoryError after uploading
Is MySQL involved per chance?
cheers.
___
Andrew Lindesay
technology : www.lindesay.co.nz
business : www.silvereye.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/sam%
40360works.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
