From: =?iso-8859-1?B?TOFzemzzIFRpYm9y?= <ltibor@mail.tiszanet.hu>
To: <pgsql-interfaces@postgresql.org>
Subject: RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour
Date: Fri, 9 Feb 2001 12:02:37 +0100
Message-ID: <NEBBJDDFALKDHFBLCGCPGEANCAAA.ltibor@mail.tiszanet.hu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-reply-to: <4.3.2.7.2.20010208124747.00c3e860@mail.merge.com>
Importance: Normal

> I found another slight behavior change with the Linux
> client ODBC library between 7.0.3 and the 7.1 beta 3
> release.  We are running under Redhat 6.0.
>
> We have set the ODBC driver in autocommit off mode.  With
> the 7.0.3 driver, a BEGIN was automatically issued
> before the driver encountered a INSERT/UPDATE/DELETE.  With
> the 7.1 beta 3 ODBC driver, it now also issues a BEGIN when it
> encounters a SELECT.
>
> Is this the expected behavior under 7.1?

I think it can be. (We assumed this behavior a year ago.) Sometimes we
need transaction time in the beginning of a transaction. We can get it with
a
SELECT. Because the transaction can begin only with an update statement,
we must do a workaround - until now.

> I actually found the problem because our code does a number
> of queries against the database, and then issues a
> VACUUM ANALYZE.  This stopped working with the 7.1 beta 3.

What the SQL specs say? Could this behavior an option in the driver?

Regards, Tibor

--
Tibor Laszlo
ltibor@mail.tiszanet.hu