On Fri, Mar 16, 2012 at 5:02 AM, Kjell Rilbe <kjell.rilbe@...> wrote:

>
> 1. Modify the application to be able to connect to a "real server", i.e.
> don't use embedded Firebird. This would also require a complete overhaul
> of the sourcecode to make sure it handle concurrency and update
> conflicts correctly. In other words: if client A loads some data and
> modifies it, during which client B also loads the same data and modifies
> it in a different manner and saves it, what should then happen when
> client A tries to save its modification, in conflict with B's changes?
> This may or may not be a lot of work.
>

Almost certainly less work than figuring out how to merge the two sets
of changes in a replication scenario.

I agree with Kjell that 1 is the right answer, but demur slightly on the
difficulty. You (or rather your programmer) has to learn the "rollback"
command and to recognize a few classes of errors that require a rollback
and retry.

Cheers,

Ann


[Non-text portions of this message have been removed]