On Jul 1, 1:02 am, Chouser wrote:
> On Tue, Jun 30, 2009 at 8:37 AM, Rowdy Rednose wrote:
>
> > Would it be easy to implement an in-memory database in clojure that
> > allows concurrent access?
>
> > It sounds pretty easy, as most of the features are already provided by
> > Clojure. I'm not sur
I'm just trying to once and for all find or implement a clojure
solution for the simple problem that most companies (that make heaps
of money developing super boring software) have: There's relational
data like "Persons" and "Companies", that needs to be accessed and
manipulated by multiple client
On Jul 1, 8:02 am, Rowdy Rednose wrote:
>
> But it looks like I have to implement that myself - which is not a
> complaint, but I'm trying to estimate the amount of work necessary.
> But I guess I could just start with one Ref per relation and then make
> it more concurrent later - if I choose
On Jul 1, 12:02 am, Chouser wrote:
> You could wrap a Ref around every value, if you chose, to
> allow independent changes to different "rows" at the same
> time -- though this would not help when inserting rows.
I guess having millions of Refs would not perform too well. Plus you
don't need tha
On Tue, Jun 30, 2009 at 8:37 AM, Rowdy Rednose wrote:
>
> Would it be easy to implement an in-memory database in clojure that
> allows concurrent access?
>
> It sounds pretty easy, as most of the features are already provided by
> Clojure. I'm not sure though about the "locking granularity".
> Of
Would it be easy to implement an in-memory database in clojure that
allows concurrent access?
It sounds pretty easy, as most of the features are already provided by
Clojure. I'm not sure though about the "locking granularity".
Of course you don't pessimistically lock in Clojure, but if you have a
