Hi Dimitry,
unfortunately, this is not that case.
It seems this happen when we read data from an another database and
insert/update into the master one.
This is an execute block running for execute statement on external and the
target table has the trigger which increases the generator
Both generators are used this way only at after insert/update triggers on
different tables.
Maybe tomorrow whe could figure out what is wrong and can make a simple test
case.
UUID is not playing for us, to much table and business logic code to refactor
it.
András
-----Original Message-----
From: Dimitry Sibiryakov [mailto:s...@ibphoenix.com]
Sent: Tuesday, May 18, 2021 4:00 PM
To: For discussion among Firebird Developers
<firebird-devel@lists.sourceforge.net>
Subject: Re: [Firebird-devel] Replication - generators' value are not replicated
18.05.2021 14:45, Omacht András wrote:
> We have very complex and long running tests.
> We ran the simpliest, which creates hundreds of domains, tables, stored
> procedures, views, triggers and inserting thousands data into tables.
> Almost everything is ok with replication, we only have two generators that
> end in different values in the replicas (they are different from the master,
> they remain in the original state in the replicas).
I can foresee only one case when it is possible: generators are increased in
one connection and received values used in another.
PS: I suggest to use UUIDs for primary keys instead of generators.
--
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
