Dino-
It depends on the nature of your application:
If you expect to have many copies of the application running (like in a
servlet app), you'll want to release the resource (connection), otherwise
you'll have a lot of processes idling out there when they aren't needed &
may bump into other resource limits. The drawback is that it takes time to
re-establish a connection each time you need it.
As some of the other folks mentioned, using a connection pool would be the
best approach in this circumstance.
If you don't expect to have many copies of the app running, you might as
well leave the connection open & get better performance by having the
connection always ready.
-NF
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of Dino Cherian
> Sent: Friday, November 23, 2001 7:12 AM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] Where should I connect to the database?
>
>
> Hi all,
>
> I would like to know which one is the best method of
> managing database connection in Java 1.3 (with
> PostgreSQL 7.1.2 JDBC).
>
> Option 1:
> Connect to the database in the "main" function and
> disconnect on program exit. Use it throughout the life
> of the application. "Connect once and use for ever".
>
> Option 2:
> Connect to the database near the code that uses it
> and disconnect after that block of code. "Use and
> throw away".
>
> Please help me.
>
> Thanks
> Dino
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
> http://geocities.yahoo.com/ps/info1
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
