Thanks Shantanu. (Sorry for the slow reply.)
> What does a single case consist of? Is it just a result-set (as a
> consequence of running an SQL query)?. Maybe an example will help.
I can't be too specific, but a single case can be thought of as a tiny
relational database with maybe 20 tables. On
Thanks for the two posts Shantanu.
The rql and Clause examples are useful, both as potential parts of a
solution and as examples of how query/aggregation stuff may be done in
Clojure style. It is conceivable that I may end up deciding all I
need is a DSL that covers the kinds of aggregations of i
Thanks Ross, that gives me a better insight into your environment.
> In the online environment single cases are fetched from a
> database with no aggregation capability and fired at the service that
> contains the aggregation functionality.
What does a single case consist of? Is it just a result-
I looked at Tutorial D - it's pretty interesting. Here are few top-of-
my-head observations:
* Which RDBMS do you use? If you are free to choose a new RDBMS,
probably you can pick one that provides most of the computational
functionality (as SQL constructs/functions) out of the box. For
example Or
On Oct 3, 1:16 pm, Ross Gayler wrote:
> Thanks Michael.
>
> > This sounds very similar to NoSQL and Map/Reduce?
>
> I'm not so sure about that (which may be mostly due to my ignorance of
> NoSQL and Map/Reduce). The amount of data involved in my problem is
> quite small and any infrastructure ai
Thanks Michael.
> This sounds very similar to NoSQL and Map/Reduce?
I'm not so sure about that (which may be mostly due to my ignorance of
NoSQL and Map/Reduce). The amount of data involved in my problem is
quite small and any infrastructure aimed at massive scaling may bring
a load of conceptual
On Fri, Oct 1, 2010 at 17:55, Ross Gayler wrote:
> Hi,
>
> This is probably an abuse of the Clojure forum, but it is a bit
> Clojure-related and strikes me as the sort of thing that a bright,
> eclectic bunch of Clojure users might know about. (Plus I'm not really
> a software person, so I need a
Thanks Saul. That's all useful stuff. At this stage I am trying to
simultaneously work out what my requirements should be and map out the
space of implementation possibilities - so it's a matter of casting
the net as widely as possible and kicking the tyres on everything in
kicking range.
Ross
On
On Oct 2, 2:55 am, Ross Gayler wrote:
> I am looking at the possibility of finding/building a declarative data
> aggregation language operating on a small relational representation.
> Each query identifies a set of rows satisfying some relational
> predicate and calculates some aggregate function
Thanks Daniel,
That sounds like it's in the right direction (although that is
probably true of anything that gives database-like functionality).
I would need some filtered-join-like functionality between tables in
order to select some of the rows of interest.
As to the declarative part: leaving
Hi Ross,
I am working on something that may be of help to you, but it's very
early in development.
Basically I wanted to see if I could write a database server in
Clojure and what I have now sounds (kinda) like what you're after. It
was really simple.
Imagine a list of maps as a database
Hi,
This is probably an abuse of the Clojure forum, but it is a bit
Clojure-related and strikes me as the sort of thing that a bright,
eclectic bunch of Clojure users might know about. (Plus I'm not really
a software person, so I need all the help I can get.)
I am looking at the possibility of fi
12 matches
Mail list logo