Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: outOfMemoryError
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Dave Cramer <pg(at)fastcrypt(dot)com>
- Cc: Vidas Makauskas <vms(at)centras(dot)lt>, pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: outOfMemoryError
- Date: Tue, 29 Aug 2006 19:47:13 -0500 (EST)
On Tue, 29 Aug 2006, Dave Cramer wrote:
This design is limited by memory. You would be far better off inserting directly instead of using a ResultSet
Actually I think there is a point to be made here. If the ResultSet is not scrollable then there is no need to store all the inserts that are made to it, so there should be no memory limit.
Kris Jurka
- Follow-Ups:
- Re: outOfMemoryError
- From: Dave Cramer
- Re: outOfMemoryError
- References:
- outOfMemoryError
- From: Vidas Makauskas
- Re: outOfMemoryError
- From: Dave Cramer
- Re: outOfMemoryError
- From: Vidas Makauskas
- Re: outOfMemoryError
- From: Dave Cramer
- outOfMemoryError
- Prev by Date: Re: outOfMemoryError
- Next by Date: Re: error: ResultSet.updateObject(timestamp in POSTGRES,
- Previous by thread: Re: outOfMemoryError
- Next by thread: Re: outOfMemoryError
- Indexes: