Since I started using triggers, checks and functions/stored procedures when modelling my databases I can no longer understand why people use MySQL.. PostgreSQL is so much better than MySQL in every single way I can think of! Looking at the MySQL TODO-list I will take a look at it again after 5.1 is released but until then I consider it a toy. At least for applications more advanced than a personal blog..
mysql flies very nicely in a heavy production environment with little maintenance. postgres, on the other hand, requires a fair amount of upkeep to keep it smooth. unless you need the advanced functionality postgres provides, mysql is a perfectly good choice for light to medium applications. if you're wanting to store a few hundred million rows of something, go buy oracle. otherwise either mysql or postgresql will fit the bill.. which you choose depends on how you use, but neither of them are necessarily a Bad cho
Think lucky. If you fall in a pond, check your pockets for fish.
-- Darrell Royal
I used to swear by MySQL (Score:3, Insightful)
Postgres is where it is at.
Re:I used to swear by MySQL (Score:2)
Since I started using triggers, checks and functions/stored procedures when modelling my databases I can no longer understand why people use MySQL.. PostgreSQL is so much better than MySQL in every single way I can think of! Looking at the MySQL TODO-list I will take a look at it again after 5.1 is released but until then I consider it a toy. At least for applications more advanced than a personal blog..
Re:I used to swear by MySQL (Score:0)
environment with little maintenance. postgres,
on the other hand, requires a fair amount of
upkeep to keep it smooth. unless you need the
advanced functionality postgres provides, mysql
is a perfectly good choice for light to medium
applications. if you're wanting to store a few
hundred million rows of something, go buy oracle.
otherwise either mysql or postgresql will fit
the bill
use, but neither of them are necessarily a Bad
cho