Re: Automatic transactions in SELECT

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.