[wplug] MySQL Mirror/Clustering

[George Gensure]

Postgres has some pretty-pretty cool strengths, though I'm pretty sure
that you won't need to use a lot of these.  Basically if all you need
is a bit-bucket, MySQL will do you well.  If you need some esoteric
features or elegant interfaces, postgres is your baby

Views: to my knowledge you can't have views in MyISAM
Triggers: cmon, even sqlite supports triggers.  Even if MySQL
supported this, with postgres's pluggable language system, you can
write your triggers/functions in perl, python, ruby and anything else
you want.
Ref. Integrity:  No foreign keys in MyISAM (though they are supported in InnoDB)
Programmable Functions: write something fresh and new, in any language
you choose
subselects: pain in the ASS to do simple subselect activities in MySQL
sql99 conformance:  no other db that i know of has this kind of conformance.
schemas: relegate all of your related db objects to a particular table

lots of other goodies to be found on the postgresql website (www.postgresql.org)

-George

On 7/11/05, Shane Liesegang <shane at techie.net> wrote:
> On Mon, 11 Jul 2005, George Gensure wrote:
> 
> > Just don't try to put any referential integrity, triggers, data types
> > or functions into your application and you'll do fine.
> >
> > Making MySQL more reliable and fault-tolerant usually = switching to postgres.
> >
> > just my two cents.
> >
> 
> Well, I'm open to that possibility if it really provides what I need in a
> better fashion. I've looked around for a neutral comparison of the two
> systems, but haven't really heard a compelling reason to use PostgreSQL
> over MySQL. I'd hate to start a flame-fest, but what do people see as the
> inherent strengths in both platforms?
> 
>         - SJML
> 
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug
>