On Tue, Jan 3, 2012 at 3:06 PM, Dmitry Yemanov <firebi...@yandex.ru> wrote:
> > In the past, I liked the idea to wrap the txn IDs, but now I'm more and > more keen to consider other solutions instead. > Completely agree - including having changed my mind. I agree with Dimitry S. that his replicate/backup/restore/reverse strategy works, assuming that the load is light enough that the newly restored replicant can eventually catch up. At the same time, one of Firebird's strong points is the limited amount of expertise necessary to manage the system, so in the longer run, either a variable length transaction id or a record version by record version flag indicating the size of the transaction id has a lot of merit. Best regards, Ann ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
