Re: Feature discussion: Should syntax errors abort a transaction?

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Feature discussion: Should syntax errors abort a transaction?
Date: 2012-06-23 12:18:40
Message-ID: js4c70$se5$1@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2012-06-19, Rafal Pietrak <rafal(at)zorro(dot)isa-geek(dot)com> wrote:

> And we are talking about interractive psql breaking transaction because
> of syntax error - almost always this is a one time typo. I'd prefere it
> to be a bit more "sloopy", then deployed SQL application (e.g.
> non-interactive session).

possibly you could program keyboard macros to handle savepoints to
have an easy way to recover from these errors, but if you're working on a
busy database keeping a transaction open whislt you think about syntax
is going to cost perfromance for the other users.

--
⚂⚃ 100% natural

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joe Van Dyk 2012-06-23 22:03:42 row_to_json question
Previous Message Jasen Betts 2012-06-23 11:44:54 Re: Extensions and roles for access administration