9/5 Stupid Questions:
Postgre SQL seems to be a better Database, but why MySQL,
which lack of nested queries, foreign key, and other major feature,
seems to be used more in the real world than Postgre?
\_ Because it's comparatively easy to set up, and is "good enough".
It's the microsoft syndrome.
\_ Postgres isn't hard to setup. In fact, it's very easy.
\_ yeah, it is cake. Was mysql first? I suspect this is just
one of those critical mass things. MySQL was first to reach
100 monkeys. I used mysql first because all the hip PHP kids
were using it, saying how great it was and that it was the
fastest thing out there, when i set up my apache-php and wanted
a database a couple years ago. I just recently installed
PostgreSQL -crebbs
\_ I first started out using MySQL, and liked it well enough.
Eventually I moved to postgres, but I've found some things that
irk me a bit. Getting PGSQL to allow network connections to
the database was one hoop. Trying to add columns to a table,
and giving that column a default value and placing restrictions
on it (NOT NULL) doesn't seem to work under postgres. Admittedly
I haven't used it that much to try to REALLY work past these
problems, but that's one man's 10,000 foot view. --sowings
\_ There are still good reasons to use MySQL. It's optimized for
_read_ performance, both from a speed and integrity point of view.
If you're rarely putting data in in large quantities, and have tons
and tons of accesses, and you know how to guarantee integrity
yourself, MySQL might be a good choice.
\_ philcompress! philcompress! philcompress is the STANDARD!
way to efficiently store data without guaranteeing integrity! |
http://csua.com/feed/