| Subject | two-way replication |
|---|---|
| Author | turbomenda |
| Post date | 2004-01-27T08:38:39Z |
--- In firebird-support@yahoogroups.com, "Dimitry Sibiryakov"
doesn't have the IBPReplicator limits you mention. It's am using it
succesfuly ever since in quite a busy enviroment with 5 1GB replicas
and hudreds of thousands of operations per day.
I call it two-way replication, because it allows updates to any
record in any replica, unlike most replication systems available back
in the days I wrote it - that required logicaly dividing the DB into
exclusive pools of PKeys.
It works realtime (can work offline too)
If there's people in the Firebird society interested in developing it
into something everybody could use, please contact me on priv.
Job offers welcome, too :-)
> Primary keys must be constant (Updating PK value will confusecurrent
> version of replicator).Some 3 years ago I wrote a IB replication system of my own that
> Cascade delete will cause a lot of warnings on replication.
doesn't have the IBPReplicator limits you mention. It's am using it
succesfuly ever since in quite a busy enviroment with 5 1GB replicas
and hudreds of thousands of operations per day.
I call it two-way replication, because it allows updates to any
record in any replica, unlike most replication systems available back
in the days I wrote it - that required logicaly dividing the DB into
exclusive pools of PKeys.
It works realtime (can work offline too)
If there's people in the Firebird society interested in developing it
into something everybody could use, please contact me on priv.
Job offers welcome, too :-)