[om-list] Re: Why not MySQL page

[Mark Butler]

The first section of this page is pretty accurate, if a bit inflammatory.  The
comments get redundant very quickly.

There is really only one reason to use MySQL over Postgres and that is raw
speed.  The main reason not to use MySQL for a multi-user system is the
concurrency problems due to table level locking.  We could probably live
without transaction support, but it makes life a lot easier.

The multi-version concurrency control of databases like Postgres is ideal if
you want multiple users to run complex, long running transactions
simultaneously.

In general, however, Postgres is about two generations ahead of MySQL in
internal architecture and comes with a long list of useful features that have
been standard in industrial strength relational databases for about a decade.

If I were writing a single user or a read-only system I would consider MySQL
very seriously, however.

- Mark

Lee Howard wrote:
> 
> At 07:06 AM 3/30/01 -0700, Luke Call wrote:
> >Here's one guy's views on why to use postgresql instead of mysql for
> >certain applications, of which ours is probably one. It's interesting:
> >      http://openacs.org/philosophy/why-not-mysql.html
> 
> No offence intended, but this reads like a bunch of technical bickering.  I
> don't know how anyone is to come to any real conclusion about what's best
> for them by reading it.  In most situations such as this I've approached
> the solution by testing both and choosing whatever performed or suited me
> better.  I do that simply because I do a lot of consulting, and it benefits
> me to know my own preference in my line of applications.  In our case,
> maybe it's not worth the bother.
> 
> >I am agreeing with Mark now that postgresql sounds good, and whatever
> >web server and servlet engine. Pretty cool that such things are
> >available free. Lee, what do you think?
> 
> It doesn't really matter to me.  PostgreSQL or MySQL - I think we're going
> to get as much benefit from one as from the other.  I'm still quite vague
> on the actual intended table structure and intended types of queries, which
> I would need to understand before I could suggest a technical opinion.  But
> honestly, I doubt that it would make a difference.
> 
> >Does Lee or Mark prefer to set
> >these up?
> 
> No preference.
> 
> Lee.
> 
> > We'll probably want the web server/servlet engine to be
> >physically close to the database, for performance reasons.
> >
> >Sounds like we have our tools pretty much nailed down for the moment.
> >
> >Luke
> 
> _______________________________________________
> om-list mailing list
> om-list at onemodel.org
> http://www.pairlist.net/mailman/listinfo/om-list

-- 
Mark Butler	       ( butlerm at middle.net )
Software Engineer  
Epic Systems              
(801)-451-4583