"gavino" <bootiack (AT) yahoo (DOT) com> writes:

In 1995 Oracle was too heavy, msql was too light, and Postgresql wasn't
ready for production use.

There's a lot I could say in answer to your question, gavino, but I
don't have time. Other people who could effectively answer your
question hang out in comp.databases. I'm crossposting and setting
followups there.

Only the slight beginning of an answer: By setting constraints on the
back end of your application using a relational database, you reduce the
number of possible ways to cause disaster, letting one hack a little
more freely on the front end.

--

http://ourdoings.com/ Easily organize and disseminate news and
photos for your family or group.

Bruce Lewis wrote:
Stronger in which respect? It all depends on your goals.

Another reason is performance. If the data set can grow large you're
better off with a robust and mature product vs. implementing indexing
etc. yourself.

Regards

robert

using a File based data model controlled via LISP. Depending on the
application, files can bea fine way to provide data storage. If your
application does not need the features they lack (transaction control,
data isolation, SQL interface, etc.), then go ahead and use them.

Stronger? Depends on what functionality you need. I would say no,
merely because anything remotely like a DBMS must be built in the
application, and debugged in the application layer. Not the most robust
solution, IMHO.

Ed