From: Guillaume Rousse <Guillaume.Rousse@univ-reunion.fr>
To: pgsql-interfaces@postgresql.org
Cc: petermount@it.maidstone.gov.uk
Subject: RE: where to close statement ?
Date: Tue, 18 Apr 2000 17:56:45 +0400
Message-ID: <00041817580100.07659@agathe> (raw)
In-Reply-To: <1B3D5E532D18D311861A00600865478C70C4BC@exchange1.nt.maidstone.gov.uk>
References: <1B3D5E532D18D311861A00600865478C70C4BC@exchange1.nt.maidstone.gov.uk>
All right, that's another way to close them, but it doesn't answer to the
question : where to close ?
Le mar, 18 avr 2000, Peter Mount a écrit :
> I test each one, and if not null, then call close, ie:
>
> if(rs!=null) rs.close();
>
> This allows for the statement to be open, but the failure being with the
> ResultSet.
>
> Peter
>
> --
> Peter Mount
> Enterprise Support
> Maidstone Borough Council
> Any views stated are my own, and not those of Maidstone Borough Council.
>
>
>
> -----Original Message-----
> From: Guillaume Rousse [mailto:Guillaume.Rousse@univ-reunion.fr]
> Sent: Tuesday, April 18, 2000 1:25 PM
> To: pgsql-interfaces@postgresql.org
> Subject: [INTERFACES] where to close statement ?
>
>
> Hi.
> Imagine the foolowing situation: i got one connection, and i have
> several
> preparedStatements to execute, each with different parameters. Is is
> good
> practice to close the connection in a finally() statement. But what
> about
> statements and resultset ? Is there an advantage to close them
> explicitely :
> -in the finally statement, before the connection.close() (see code A) ?
> -in the try statement, between each statement execution for the
> resultset, and
> between each redefinition for each preparedStatement (see code B) ?
>
> code A:
> Connection con=null;
> PreparedStatement stmt=null;
> Resulset rs=null;
>
> try {
> stmt=...
> stmt.set...
> rs=stmt.execute();
> stmt.set...
> rs=stmt.execute();
>
> stmt=...
> stmt.set...
> rs=stmt.execute();
> stmt.set...
> rs=stmt.execute();
> } finally {
> rs.close();
> stmt.close();
> con.close()
> }
>
> code B:
> Connection con=null;
>
> try {
> PreparedStatement stmt=...
> stmt.set...
> Resulset rs=stmt.execute();
> rs.close();
> stmt.set...
> rs=stmt.execute();
> rs.close();
> stmt.close();
>
> stmt=...
> stmt.set...
> rs=stmt.execute();
> rs.close();
> stmt.set...
> rs=stmt.execute();
> rs.close();
> stmt;close();
>
> } finally {
> con.close()
> }
> --
> Guillaume Rousse
> Iremia - Université de la Réunion
>
> Sleep doesn't exists. Just lack of cafeine.
--
Guillaume Rousse
Iremia - Université de la Réunion
Sleep doesn't exists. Just lack of cafeine.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: Guillaume.Rousse@univ-reunion.fr, petermount@it.maidstone.gov.uk
Subject: RE: where to close statement ?
In-Reply-To: <00041817580100.07659@agathe>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox