Hi, I helped implementing a (commercial) synchronization solution for PointBase. It looks like the company and the product don't exist any longer. There were two solutions: one is using the transaction log file, the other using triggers / shadow tables.
I don't like the transaction log solution because synchronization is potentially slow, and needs a lot of space. Also, not all databases allow you to access the transaction log. The triggers / shadow table solution is better I believe. It works for all databases. You don't need to keep a complete copy of the old data: a cryptographically secure hash (SHA-256) value for each row (or even groups of rows) is enough. The actual solution was quite complicated, and I'm not sure if I want to implement it again. The problem is that each user has some different understanding on how it is supposed to work. There is some overlap on the required feature set, but not much. Some want a hub-and-spoke solution, some peer-to-peer. There are many possible conflict resolution ideas... Regards, Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
