20 Jan
2011
20 Jan
'11
9:32 p.m.
Hi Norbert,
The goal of Moose is to help us analyze data. This means: modeling, mining, measuring,
querying, visualizing, browsing etc. To do this, the prerequisite is being able to
manipulate the data. Right now, we have all objects in memory. To be able to scale we need
database support.
So, all in all, it's not for a specific use case, but for any model that is described
by Fame.
Cheers,
Doru
On 20 Jan 2011, at 21:06, Norbert Hartl wrote:
On 19.01.2011, at 09:39, Stéphane Ducasse wrote:
--
www.tudorgirba.com
"Beauty is where we see it."
Hi guys
in the past marco did a bridge to database for metadescribed but since famix was not
regular we could not get
famix models in databases.
So I would be interested to know if there is an ongoing effort to do that?
Because this would be a real plus for FameDescribed models. May be using Glorp and I was
thinking that this would be
good also to get all the source code of pharo in a db using Ring.
And get Torch there too.
Stef,
are there any specific requirements on the db? Is this for long time storage of a lot of
things or just to extend the main memory for a definite amount of time?
What will be the main actions to do? Searching for symbols/methods/class names or
traversing stuff?
In case you want to add over time a lot of code and want to have general search
capabilities that can be stored in a central location it might be a good idea to ask
gemstone to sponsor a full license and install this somewhere in inria. Or do I missing
the point?
Norbert
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev