pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gunnar R|nning <gunnar@candleweb.no>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Gunnar R|nning <gunnar@candleweb.no>
Cc: Peter Mount <peter@retep.org.uk>
Cc: Thies C. Arntzen <thies@digicol.de>
Cc: pgsql-jdbc@postgresql.org, PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: [JDBC] Re: PostgreSQL and PHP persistent connections
Date: 20 Mar 2001 12:59:21 +0100
Message-ID: <x61yrshcrq.fsf@thor.candleweb.no> (raw)
References: <200103192354.SAA11684@candle.pha.pa.us>

Bruce Momjian <pgman@candle.pha.pa.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). 

Cheers, 

	Gunnar



view thread (17+ messages)

Message-ID: <x61yrshcrq.fsf@thor.candleweb.no>
Permalink:  ../x61yrshcrq.fsf@thor.candleweb.no/
Also on:    postgresql.org/message-id/x61yrshcrq.fsf@thor.candleweb.no

 · 

reply

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: gunnar@candleweb.no, pgman@candle.pha.pa.us, peter@retep.org.uk, thies@digicol.de
  Subject: Re: [JDBC] Re: PostgreSQL and PHP persistent connections
  In-Reply-To: <x61yrshcrq.fsf@thor.candleweb.no>

* 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