Skip site navigation (1) Skip section navigation (2)

Re: [JDBC] Re: PostgreSQL and PHP persistent connections

From: Gunnar R|nning <gunnar(at)candleweb(dot)no>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Gunnar R|nning" <gunnar(at)candleweb(dot)no>, Peter Mount <peter(at)retep(dot)org(dot)uk>, "Thies C(dot) Arntzen" <thies(at)digicol(dot)de>, pgsql-jdbc(at)postgresql(dot)org, PostgreSQL-interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: [JDBC] Re: PostgreSQL and PHP persistent connections
Date: 2001-03-20 11:59:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfacespgsql-jdbc
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

> > Well, I think most connection pools people use are database independent -
> > when it comes to JDBC this is the case at least. 
> So what platform-indendent method do they use to see that the passed
> connection doesn't have an open transaction or some other setting?

None - it is application responsibility to not mess around with the
connections. I usually use the Command pattern from the GoF book to do my
database access. This ensures me that I have one pluggable executor that
can do all the database specific stuff, like proper pre command exec
actions, post command exec actions, exeception handling(Error codes would
be very welcome in pgsql). 



In response to

pgsql-interfaces by date

Next:From: Barry LindDate: 2001-03-20 17:57:01
Subject: Re: [INTERFACES] Trouble with JDBC2 ResultSet.getDate()
Previous:From: DI HasenöhrlDate: 2001-03-20 10:18:49
Subject: floatingpoint values and MsAccess

pgsql-jdbc by date

Next:From: Garry ThunaDate: 2001-03-20 14:00:43
Subject: Re: get the query created by PreparedStatement
Previous:From: Juhan-Peep ErnitsDate: 2001-03-20 09:25:55
Subject: Trouble with JDBC2 ResultSet.getDate()

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group