Hi,
What are the use cases you have in mind ?
2010/6/23 Timothy Baldridge :
> I'm wondering if we're going about this slightly the wrong way. Let's
> take a look at CouchDB. CouchDB prefers to keep all data on the disk
> at all times. As docs (or items) are added to a database they extend
> that
You might also want to check out Redis, which is supposed to act like
disk persistent data structures in memory. The author just added a
virtual memory module, so now Redis can handle datasets larger than
the memory you assign it.
Mark
On Jun 22, 10:57 am, Timothy Baldridge wrote:
> Greetings,
I'm wondering if we're going about this slightly the wrong way. Let's
take a look at CouchDB. CouchDB prefers to keep all data on the disk
at all times. As docs (or items) are added to a database they extend
that database, but never overwrite it. In addition all changes are
written instantly to dis
On Jun 22, 7:57 pm, Timothy Baldridge wrote:
> system it uses. Has anyone tried marrying the two system systems to
> create a truly persistent data primitive where any "updates" to a map
> is written to the disk?
There has been an attempt at integrating STM transactions with DB
transactions, even
On Jun 22, 12:57 pm, Timothy Baldridge wrote:
> Greetings,
>
> I've recently started learning Clojure. For the past year or so I've
> been using CouchDB, and am very happy with the MVCC disk storage
> system it uses. Has anyone tried marrying the two system systems to
> create a truly persistent
Not really tried that, but something that goes somewhat in the direction,
stupiddb - (see on github or explanations on my blog http://blog.licenser.net
). It is not guaranteed persistent sadly since it's not easy to couple IO and
Memory transactions and it might be a bit too heavy for a stupid d
