Re: Parser abort ignoring following commands - Mailing list pgsql-hackers

From Adam Haberlach
Subject Re: Parser abort ignoring following commands
Date
Msg-id 20010526190044.A15669@newsnipple.com
Whole thread Raw
In response to Re: Parser abort ignoring following commands  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Sat, May 26, 2001 at 05:57:16PM +0200, Peter Eisentraut wrote:
> Tom Lane writes:
> 
> > Peter Eisentraut <peter_e@gmx.net> writes:
> > > No, I think there is another problem.  How about something without
> > > selects:
> >
> > > $ psql -c 'delete from pk; delete from xx;'
> > > ERROR:  Relation 'xx' does not exist
> >
> > > "pk" exists, but nothing is deleted.
> >
> > Sure, because the transaction is rolled back.  The whole string
> > is executed in one transaction.  You will definitely break existing
> > applications if you change that.
> 
> Applications that rely on this behaviour are broken.  It was always said
> that statements are in their own transaction block unless in an explicit
> BEGIN/COMMIT block.  A statement is defined to end at the semicolon, not
> at the end of the string you submit to PQexec().
You put semicolons at the end of your strings to PQexec()?

-- 
Adam Haberlach            | At either end of the social spectrum there lies
adam@newsnipple.com       | a leisure class.  -- Eric Beck 1965 
http://www.newsnipple.com |
'88 EX500    '00 >^<      | http://youlook.org


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Parser abort ignoring following commands
Next
From: Bruce Momjian
Date:
Subject: Re: First version of multi-key index support for GiST