Hi, This sounds like a custom data synchronization solution. To support that, you either need a way to read from the transaction log, or you have to build this system yourself using a trigger / triggers.
Reading from the transaction log would be nice, but there are problems: the "old data" is not stored in the transaction log when deleting or updating (well, actually it is, in the form of compressed page backups, but that's hard to parse). There is a feature request "Support a special trigger on all tables". I will increase the priority. It would allow you to build a transaction log writer / reader / shipping mechanism. Would that be a solution for your problem? Currently you need to create a trigger for each table, which is quite a lot of work. 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.
