Igor,

I am emailing you offline but I just do not get why people are so interested in storing source code in a relational database.

We have objects, there is a known mismatch between the object and relational world. So how does the relational database help out?

Cincom has spent many man-years attempting to make STORE work well. A few grad students wrote ENVY in the 80's and it is a way superior in most ways to all other code repositories.

Has anyone at INRIA looked at ENVY?

Regards,

Reg

From: Igor Stasenko <siguctua@gmail.com>
To: Pharo-project@lists.gforge.inria.fr
Sent: Thursday, November 3, 2011 10:00:31 AM
Subject: Re: [Pharo-project] Storing all source code in a relational database

On 3 November 2011 00:20, Stephan Eggermont <stephan@stack.nl> wrote:
> ... is a waste of time and computing resources. Relational databases are optimized
> for specific usage scenarios. CAD systems and source code management systems
> are the archetypical examples of systems that are a bad fit and will kill the performance
> of a relational database. Of course 30 years later you can brute force it, but that doesn't
> make it a good idea. Git is far superior to rdb based systems for the day-to-day work
> and the analytics should be done from a ram-based object model.
>

Completely agree with you. But i think if you can store code in
database, which one to use is a matter of taste
(knowledge/availability etc).
If we could have a nice abstraction for managing sources in image,
then choosing where to store it is not a big deal.

> Stephan
>

--
Best regards,
Igor Stasenko.