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
Thomas,
My apologies for not replying sooner. Oddly Google Groups did not
flag your response as new and I missed it.
Here is the scenario: We have a network of machines connected on a
private LAN/WAN -- upwards of 500 machines -- all of which need a
synchronized copy of an embedded H2 database
Hi,
The specific need is: to capture the complete and orded list of
transactions (DML DDL) that a frontend db has commited between two
specific points in time ( Check Points) in a portable format of retained
transaction log fragment. That can be SQL batch script or any other
replay-able
Hi,
we are planning on loose replication of H2 to many nodes (upwards of 500)
using JGroups
What is the concrete use case?
I have a similar need
Also here, what is the concrete use case?
create a new feature
To suggest new features, a good approach is to provide concrete
examples
El 20/03/10 06:42, Thomas Mueller escribió:
we are planning on loose replication of H2 to many nodes (upwards of 500)
using JGroups
I thought this is for replication or remote db syncs.
The specific need is: to capture the complete and orded list of
transactions (DML DDL
Hi Neal,
right now I don't have the time to advance over this , digging the code
of tracing features.
Trace data have a big part of information needed to do a transaction log
retention (in sql) but surely isn't the best place to get this
information just a casual gift.
Other feature that probably
We looked at all the transaction logging, but found that there was no
clean way to get the DML statements. And I agree, that would really
be a great way to handle the replication, as we would essentially just
be playing back logs. Unfortunately it does not seem that there is a
way to do that
If you don't mind the trigger approach, then SymmetricDS (http://
symmetricds.org) might be a
possible solution. It has great support for H2 and has been used to
replicate/synchronize changes
out to thousands of H2 clients.
On Mar 15, 4:15 pm, Dario Fassi dfa...@gmail.com wrote:
Hi,
I have a
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
Hi,
I have a similar need and wondered if it would be possible implement
some form of transaction log retention,
based on the CheckPoint command , trace file and ConvertTraceFile tool.
El 15/03/10 16:46, ne...@glyph.com escribió:
Right now I am looking for the best way to capture changes on
10 matches
Mail list logo
