From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Steve Wranovsky <stevew(at)merge(dot)com> |
Cc: | pgsql-interfaces(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour |
Date: | 2001-02-12 23:16:32 |
Message-ID: | 3A886ED0.184C7B12@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces pgsql-odbc |
Steve Wranovsky wrote:
>
> >>
> >> Given these considerations, I think it's a mistake for ODBC to treat
> >> SELECT differently from other queries for the purpose of setting
> >> transaction boundaries.
> >>
> >
> >OK, agreed.
> >However simply putting back the behabior make it impossible to call
> >VACUUM in psqlodbc autocommit off mode.
> >
> >My idea is as follows.
> > [In autocommit off mode]
> > 1) All statements except STMT_TYPE_OTHER issue
> > "BEGIN" if a trasaction isn't in progress.
> > 2) STMT_TYPE_OTHER statements automatically issue
> > "COMMIT" if a transaction is progress.
> >
> >Comments ?
>
> I now agree with point 1 above, but for point 2, I believe you should
> force the user to issue a COMMIT if a transaction is in progress
> when they try a VACUUM ANALYZE.
I've been waiting for reply.
I see. It's the simplest change. But you seem to have to
change your existent your code. Or you may have to distinguish
your code according to PG servers. Is it OK ?
Regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Jouni Ahto | 2001-02-12 23:19:26 | Re: [PHP-DEV] Re: Re: PostgreSQL and PHP persistent connections |
Previous Message | Bruce Momjian | 2001-02-12 17:25:37 | Re: Re: PostgreSQL and PHP persistent connections |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2001-02-12 23:44:17 | Re: RE: [PATCHES] Re: [HACKERS] 6.2 protocol |
Previous Message | Steve Wranovsky | 2001-02-12 16:37:00 | Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour |