On 10 Mar 2014, at 12:58pm, Adam Devita <adev...@verifeye.com> wrote:
> Are the databases designed to allow you to perform such an operation easily?
>
> On the databases I do it with, I have designed in enough extra data in the
> db and logic in my code to handle sorting out what to do (which record to
> use) if both databases have different data with the same primary key.
That's one of the problems. Another is what happens if these two commands get
executed on different copies of the databases:
INSERT INTO customers (name, city) VALUES ("Smith Vacuum Depositing", "Newport")
UPDATE customers SET city = "Fountain City" WHERE city = "Newport"
Without knowing the intention behind the UPDATE (rather than just a dry record
of SQL commands) there's no way to tell what city should be recorded for Smith.
Sometimes a city is renamed. Sometimes it's a change that just happens to
effect all data already entered.
There are many other problems like this. Put them all together and you know
why synchronization of SQL databases is not a solved problem.
Simon.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
