Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: extra rowcopy in ResultSet allways needed ?.
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Gustav Trede <gustav(dot)trede_wsdevel(at)telia(dot)com>
- Cc: pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>
- Subject: Re: extra rowcopy in ResultSet allways needed ?.
- Date: Wed, 20 Feb 2008 12:18:43 -0500 (EST)
On Wed, 20 Feb 2008, Gustav Trede wrote:
here is diff from current cvs.
Patch applied, thanks. The one minor change I made was to set rowBuffer = null instead of rowBuffer = this_row in the non-updatable case to catch any potential issues where the rowBuffer was being used improperly.
Kris Jurka
- References:
- extra rowcopy in ResultSet allways needed ?.
- From: Gustav Trede
- Re: extra rowcopy in ResultSet allways needed ?.
- From: Kris Jurka
- Re: extra rowcopy in ResultSet allways needed ?.
- From: Kris Jurka
- Re: extra rowcopy in ResultSet allways needed ?.
- From: Kris Jurka
- Re: extra rowcopy in ResultSet allways needed ?.
- From: Gustav Trede
- extra rowcopy in ResultSet allways needed ?.
- Prev by Date: Re: Retrieving last InsertedID : INSERT... RETURNING safe ?
- Next by Date: Problem executing remote SELECT's (through internet) with JDBC
- Previous by thread: Re: extra rowcopy in ResultSet allways needed ?.
- Next by thread: jdbc and nfs
- Indexes: