Date: Fri, 24 Dec 1999 10:56:33 +0100
From: Michael Meskes <meskes@postgresql.org>
To: Robert Rothe <rrothe@mindspring.com>
Cc: "pgsql-interfaces@postgreSQL.org" <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] Always get TranBlock notice using 'c'
Message-ID: <19991224105633.B357@fam-meskes.de>
Mail-Followup-To: Robert Rothe <rrothe@mindspring.com>,
	"pgsql-interfaces@postgreSQL.org" <pgsql-interfaces@postgresql.org>
References: <38628B50.FF9F52B7@mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
In-Reply-To: <38628B50.FF9F52B7@mindspring.com>;
	from rrothe@mindspring.com on Thu, Dec 23, 1999 at 03:51:28PM
	-0500

On Thu, Dec 23, 1999 at 03:51:28PM -0500, Robert Rothe wrote:
> When writing apps using 'c' and the preprocessor, I always get a
> "NOTICE: BeginTransactionBlock not in default state" with my first BEGIN

If you want to expclicitely call BEGIN you either have to call ecpg with
option '-t' to change the default value or issue a EXEC SQL SET AUTOCOMMIT ON
in your program.

> statement.  I've tried placing a COMMIT and END at the beginning of the
> app, but then I just get a NOTICE on the commit and another one on the
> BEGIN.

The default of ecpg is that it creates a transaction for all your action
automatically and you just issue COMMITs. After a COMMIT ecpg issues a BEGIN
all by himself. With SUTOCOMMIT set to ON ecpg uses the same logic as psql
for instance, namely that each statement is a transaction of its own unless
you issue a BEGIN.

Michael
-- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael@Fam-Meskes.De           | Use PostgreSQL!