Re: [HACKERS] Parser abort ignoring following commands

2001-05-26 Thread Adam Haberlach
On Sat, May 26, 2001 at 05:57:16PM +0200, Peter Eisentraut wrote: > Tom Lane writes: > > > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > > No, I think there is another problem. How about something without > > > selects: > > > > > $ psql -c 'delete from pk; delete from xx;' > > > ERROR: Relat

Re: [HACKERS] Parser abort ignoring following commands

2001-05-26 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: >> 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 > t

Re: [HACKERS] Parser abort ignoring following commands

2001-05-26 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> 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.

Re: [HACKERS] Parser abort ignoring following commands

2001-05-26 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > psql -c 'select * from pg_class; select * from no_such_table;' > Shouldn't this at least give me the result of the first select before > aborting the second? The behavior you are complaining of is not the backend's fault. The reason it acts that way