IIRC, set transaction is local to isql, and is parsed to determine the actual
tpb to use. He uses set transaction <options>, which starts the transaction
with the specified options. If you then commit and execute another query, then
a new transaction is started implicitly. This transaction - apparently - uses
the default, and not the previously specified transaction options.
Personally, I'd expect the previously used transaction options to be used until
a new explicit set transaction is executed.
Mark
----- Reply message -----
Van: "Dimitry Sibiryakov" <s...@ibphoenix.com>
Aan: "For discussion among Firebird Developers"
<firebird-devel@lists.sourceforge.net>
Onderwerp: [Firebird-devel] SET TRANSACTION in isql
Datum: ma, sep. 14, 2015 21:33
14.09.2015 21:22, Helen Borrie wrote:
> Could some isql boffin confirm, or explain?
isql does not start transaction itself. It just send SET TRANSACTION query to
server as
is. Server don't use any kind of "history of session", so it can use only these
flags that
are set in command itself. Thats why "SET TRANSACTION" without further options
will start
default (concurrency-level) transaction. No matter what happened in the past.
--
WBR, SD.
------------------------------------------------------------------------------
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
------------------------------------------------------------------------------
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
