No.  By default a request is committed if it finishes normally and
rolled back if it's terminated by an uncaught exception, but can be set
to require an explicit commit or rollback.  There is, however, no
transaction prepare call as two phase commit is automatic.

I should have mentioned that events are under transaction control --
dropped on the floor if the transaction rolls back and otherwise sent
after the transaction has committed, but that was true of Interbase
events as well.


On 10/7/2019 10:53 AM, Dimitry Sibiryakov sd@...
[Firebird-Architect] wrote:

> 07.10.2019 16:47, Jim Starkey jim@... [Firebird-Architect] wrote:
>> As for the problem of a slow message receiver, AmorphousDB is a pure server; if
>> unprocessed event stack up in a client process, that his problem and not mine.
> Do I remember right that in AmorphousDB you have no explicit transactions and every
> statement is always in auto-commit mode?
>
>

--
Jim Starkey