From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Glen Parker" <glenebob(at)nwlink(dot)com> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Driver confused by explicit transactions |
Date: | 2002-12-08 00:51:31 |
Message-ID: | EKEJJICOHDIEMGPNIFIJIEAMKAAA.Inoue@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Glen Parker [mailto:glenebob(at)nwlink(dot)com]
>
> > > It appears there is a somewhat on-going bug in the ODBC driver
> > > (07.02.0005 in this case) concerning explicit transactions. The
> > > following sequence demonstrates it.
> >
> > What do you mean by explicit transactions ? i. e
> >
> > > Begin transaction (OK)
> >
> > How do you begin the transaction ?
>
> By turning off auto-commit with a call to SQLSetConnectOption().
>
> > > Execute update statement(s) (OK, records hidden from other
> > > transactions)
> > > Commit transaction (OK, records appear to other transactions)
> >
> > And how do you commit the transaction ?
>
> With a call to SQLTransact() to either commit or abort transaction.
Should SQLTransact() turn on auto-commit ?
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2002-12-08 03:47:35 | Access and rules |
Previous Message | Glen Parker | 2002-12-07 23:27:08 | Re: Driver confused by explicit transactions |