🚀 go-pugleaf

Daniel Alvarez wrote:
[snip]
> My question is if there is a solution or workaround to solve this with IB
> Replicator, and I wanted to know if SQL Server and Oracle replication works
> the same as Interbase one.
> 
> Are they smart enough to get rid of this problem?

The built-in oracle replication sure is able to do it, I'm making a 
manual one (so don't need to build oracle enterprise to do it) and I 
solved it in the following way:

1) first, I made all constraints deferrable, so with a single system 
switch I make them only enforceable at commit time
2) when copying, always replicate to the current time, no matter how 
many log entries and what entries you have, unless you have a way to do 
that (the only way I know is copying all the data to another table -> db 
slowdown). First, change session transaction level to serializable, so 
you don't get other users changes in midle way (consistency), and them 
get all the records affected looking at the log. If the record was 
deleted, I get only the key in the log. When applying, first delete, 
then insert/update. I always test if the record exists, update, 
otherwise, insert.

Solerman