mysql viability (was: shells and bells)

[mikebw at colossus.bilow.com (Mike Bilow)]

This is not the way things are done.  In the "real world," the database is
part of the infrastructure and it is common to all projects.  This allows
it to be managed, backed up, and so forth.  Choosing a database server on
a per-project basis is like choosing your mail transport agent on a
per-message basis.  "Well, this one is going to a mailing list, so I guess
we can send it with exim.  And this one is going to someone whose machine
is unreliable, so we should use Sendmail."  You see my point?

-- Mike


On 2000-05-04 at 12:59 -0500, Mark Donnelly wrote:

> It comes down to the right tool for the job.  For some 
> jobs, MySQL is the right tool.  For some jobs, PostGres 
> is the right tool.  For some jobs, Oracle is the right 
> tool.  And, for some jobs, Berkeley DB is the right 
> tool.  Just like the subway is the right tool for me to 
> get to work in the morning, rather than a car.  Just 
> like Linux might be the right tool for you, rather than 
> NT.  Just like FreeBSD might be the right tool for you, 
> rather than OpenBSD.  


-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).