From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Raymond O'Donnell" <rod(at)iol(dot)ie>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Connections sitting idle... |
Date: | 2002-12-05 11:53:08 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B8128D07@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Raymond O'Donnell [mailto:rod(at)iol(dot)ie]
> Sent: 05 December 2002 09:53
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Connections sitting idle...
>
>
> ...and on 5 Dec 2002 at 8:06, Dave Page wrote:
>
> > I'm pretty sure this is the underlying ADO. It's for this
> reason that
> > pgAdmin can't drop databases - no matter how you tell ADO
> to close the
> > connection , it 'helpfully' keeps it open preventing you from ever
> > dropping that database.
>
> Does you mean that ADO keeps the connection open regardless of
> whether or not connection pooling is turned on? Is there any way to
> control this behaviour? I don't see anything in the properties of the
> ADO connection object to affect this, but maybe I just missed it at
> 2.00 am..... :)
Yes, that's the conclusion I came to. I've yet to find a way around the
problem :-(
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-12-05 12:16:46 | Re: Schemas and ODBC driver. |
Previous Message | Raymond O'Donnell | 2002-12-05 10:49:39 | Re: Connections sitting idle... |