From: | Joseph Pravato <joseph(dot)pravato(at)nomagic(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Automatic transactions in SELECT |
Date: | 2013-02-28 22:50:55 |
Message-ID: | 512FDF4F.8030502@nomagic.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
> This is viewed as a feature since otherwise, in the absence of
> careful exception handling, you might commit a transaction after an
> important step failed, possibly resulting in data loss.
> Due to the desire of members of the community not to lose data due
> to a script file typo, any suggestion that a transaction continue
> to process subsequent statements after an error without a
> subtransaction is a non-starter. Maybe you can change the
> SquirrelSQL source code to have a feature for this, like psql does?
That's sad to hear, unfortunately if that is the case we're probably going to have to do what you recommended by switching applications or
adding save points in by hand.
We appreciate all your help.
From | Date | Subject | |
---|---|---|---|
Next Message | dmp | 2013-03-01 01:21:40 | Re: Automatic transactions in SELECT |
Previous Message | Joseph Pravato | 2013-02-28 20:43:26 | Re: Automatic transactions in SELECT |