>> Sorry for the blind noise.
It is not noise.
Is there a way to configure replication to always replicate generator change?
I as as we use genertors also as settings. E.g. we change it from 1 to 0 and
back.
And in procedures or triggers we check for value in generator if it is 1 (on)
or 0 (o
18.05.2021 15:33, Karol Bieniaszewski wrote:
I as as we use genertors also as settings. E.g. we change it from 1 to 0 and
back.
And in procedures or triggers we check for value in generator if it is 1 (on)
or 0 (off).
This usage is no-go in master-slave setting because the procedures and tr
devel] ODP: Replication - generators' value are
notreplicated 18.05.2021 15:33, Karol Bieniaszewski wrote:> I as as we use
genertors also as settings. E.g. we change it from 1 to 0 and back.> And in
procedures or triggers we check for value in generator if it is 1 (on) or 0
(off). This usa
18.05.2021 16:22, liviuslivius wrote:
But such replica cannot became "master" database if master is
broken/unavailable?
Why? Values of generators used as flags are usually not important and are reset to
defaults by application after promoting as if primary server has been suddenly aborted
