Hi, I have an application where we are planning on loose replication of H2 to many nodes (upwards of 500) using JGroups. The database is read- mostly, so there will not be much replication traffic.
Right now I am looking for the best way to capture changes on the "primary" before blasting them out to the "secondaries". Ideally, I would be able to catch the CRUD/DML SQL so that I can just sent that along to all of the secondaries. This is particularly desirable as bandwidth would be kept to a minimum. However, it does not look like there is a good way to do that. So far we have looked into: * JDBC proxy to get the information out. Possibly the cleanest solution, * Using triggers. This gives me objects, both new and old, but that is not something that would work well shipping to the secondary H2s as it can be large as well as requiring "diffing" to get the actual change set. * Getting the change set out of JPA 2.0. This does not work in all situations. I expect there is a better way to do this. Thanks in advance for your thoughts on this issue. Regards, Neal -- 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.
