Hi,

Currently this is not supported.

Would it be possible to use the DatabaseEventListener or the Trigger
interface instead?

What is your use case?

Regards,
Thomas



On Wed, Jan 9, 2013 at 12:14 PM, Lutz <[email protected]> wrote:

> Hi there,
>
> I am currently experimenting with implementing a method for supporting
> replication for the H2 DB and I was wondering:
>
> Is it possible to read out the transactionlog of the database continuously?
>
> I already looked at the method in the Recover-tool that already exists but
> I can't seem to get it working correctly with this method.
>
> I would really appreciate some insight into how it works exactly, so that
> I can try to implement this.
>
> I need a way to read the transactionlog continuously in order to react to
> any transactions that will alter the database.
>
> Maybe someone can help me.
>
> Regards,
> Lutz
>
> --
> You received this message because you are subscribed to the Google Groups
> "H2 Database" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/h2-database/-/VhDVKmObvUQJ.
> 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.
>

-- 
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.

Reply via email to