Disable automatic transaction for SQLs already containing a transaction #675

Related to #568.

When trying to execute an SQL containing a transaction, the app ignores it and adds its own transaction(s). As pointed out by @chrisjlocke, canceling an import leaves the already inserted data up until the cancellation. It should instead leave the transaction in place and disable the transactions per statement added by the app.