Dear Mike,

currently, all server operations are logged as plain text and shortened to a maximum of 1000 characters per single command. If you want to have more control on logging, and provide it on a higher level, you can e.g. use functions like file:append() to write your own logs to disk [1].

We may introduce more advanced logging and recovery/rollback mechanisms in future versions of BaseX.

Best, Christian

[1] http://docs.basex.org/wiki/File#file:append ___________________________

On Wed, May 16, 2012 at 11:01 AM, Mike Hawkes mikehawkes@me.com wrote:

Actually, I would love this too - is there any chance of providing a log file option to allow the log to contain XML rather than text? Each query could then have a <query/> tag - a simple process then to read in all queries and recreate the entire database, to any given point?

Cheers Mike

On 16 May 2012, at 09:59, Andreas Weiler wrote:

Hello Gilles,

you could probably have a look at the event framework of BaseX to forward updates:

http://docs.basex.org/wiki/Events

However if serverB is read-only? How would you write the updates to that one?

-- Andreas

Am 16.05.2012 um 10:43 schrieb Gilles CARRY:

Hello,

Is there any simple way to perform a one-way replication with BaseX? The needed replication is: serverA -> serverB Where serverB is read-only. I would imagine a basic system such as server forwarding updates to server. Or more simply, is there any logging of the update queries so we can just feed them to serverB?

Thank-you, Best regards, Gilles. _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

---

BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

---

BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk