08.11.2014 13:04, Frank Schlottmann-Gödde wrote:
> What about setting a context variable telling your triggers to tag this
> changes as log only.
There is no "my triggers". And "no replication" TPB clumpet is exactly such
kind of
context variable on transaction level.
--
WBR, SD.
--
On 06.11.2014 19:44, Dimitry Sibiryakov wrote:
> 06.11.2014 19:24, Mark Rotteveel wrote:
>> I don't really understand why you would want to disable replication for
>> a single transaction.
>
> There may be a number of reason. The main one is that this transaction is
> performed by
> replicator
07.11.2014 19:58, Jim Starkey wrote:
> Statement level multi-master replication is basically
> impossible to get right, so you need to pick among a set of bad
> options. There about a billion things that can go wrong (consider a
> timestamp or random number generator, for example) that requires
On 11/6/2014 10:40 AM, Dimitry Sibiryakov wrote:
> Hello, All.
>
> I wonder if SQL standard says something about syntax of transaction's
> option for
> disabling replication of changes made by this transaction?
>
I might be wrong, but I think this whole topic needs a more than a bit
more
06.11.2014 19:24, Mark Rotteveel wrote:
> I don't really understand why you would want to disable replication for
> a single transaction.
There may be a number of reason. The main one is that this transaction is
performed by
replicator and I don't want changes to be bounced back in bidirectio
On 6-11-2014 16:40, Dimitry Sibiryakov wrote:
> Hello, All.
>
> I wonder if SQL standard says something about syntax of transaction's
> option for
> disabling replication of changes made by this transaction?
There is no such option, the syntax is:
::=
SET [ LOCAL ] TRANSACTION
::=
Hello, All.
I wonder if SQL standard says something about syntax of transaction's option
for
disabling replication of changes made by this transaction?
--
WBR, SD.
--
Firebird-Devel mailing list, web interfac
