The history is there until you archive (move a checkpoint out into a separate
directory) it and then delete the archive yourself.
the checkpointing just reduces the recovery time (i.e creates a fixed point in
time), if you were to keep all the checkpoint/archives then you would have the
Ok, cool. Any idea if you can get a list of events, or can you just get the
latest state?
Thanks,
Rich
On Oct 19, 2012 3:53 AM, Neil Davies semanticphilosop...@gmail.com
wrote:
The history is there until you archive (move a checkpoint out into a
separate directory) it and then delete the
Right now acid-state always tries to restore everything up through the
latest events.
The long term plan is to create an acid-state tool that would allow
you to rollback the event log, list and examine specific events, etc.
So, it is possible in theory, and not even that hard, but no one has
Hey all,
I've been looking at acid-state as a possible storage backend for an
application. It looks like it fits my needs pretty damn well, but one
thing that I'm curious about is if it is possible to get a list of
update events. You can obviously query for the current state, but
it's not
On Tue, Dec 13, 2011 at 4:55 AM, Anatoly Yakovenko
aeyakove...@gmail.com wrote:
So I am trying to understand how acid state works. The HelloWorld
example has a
type Message = String
data Database = Database [Message]
$(deriveSafeCopy 0 'base ''Database)
-- Transactions are defined to run
Ah, i think i get it.
On Tue, Dec 13, 2011 at 12:48 AM, Felipe Almeida Lessa
felipe.le...@gmail.com wrote:
On Tue, Dec 13, 2011 at 4:55 AM, Anatoly Yakovenko
aeyakove...@gmail.com wrote:
So I am trying to understand how acid state works. The HelloWorld
example has a
type Message = String
So I am trying to understand how acid state works. The HelloWorld
example has a
type Message = String
data Database = Database [Message]
$(deriveSafeCopy 0 'base ''Database)
-- Transactions are defined to run in either the 'Update' monad
-- or the 'Query' monad.
addMessage :: Message - Update
