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 Lind||Date: 2001-03-20 17:57:01|
|Subject: Re: [INTERFACES] Trouble with JDBC2 ResultSet.getDate()|
|Previous:||From: DI Hasenöhrl||Date: 2001-03-20 10:18:49|
|Subject: floatingpoint values and MsAccess|
pgsql-jdbc by date
|Next:||From: Garry Thuna||Date: 2001-03-20 14:00:43|
|Subject: Re: get the query created by PreparedStatement|
|Previous:||From: Juhan-Peep Ernits||Date: 2001-03-20 09:25:55|
|Subject: Trouble with JDBC2 ResultSet.getDate()|