Quoting Rich Payne [EMAIL PROTECTED]:
If you're doing any serious sort of web application my suggestion would
be to make it as DB neutral as possible. It makes it a little more
painful
at first as you can't necessarily make use of feature X of database Y
but
later on this usually pays
My quick rules of thumb:
1: If your data is fairly simple, use MySQL. If your data has complex
relationships or you need referential integrity, use PostgreSQL.
2: If you read mostly, use MySQL. If you write frequently, use PostgreSQL.
3: If your queries are simple:
select * from a
On Sun, 2002-02-17 at 12:58, [EMAIL PROTECTED] wrote:
I don't believe that MySQL has support for record locking (I may be
wrong)
This is correct.
and it definitely doesn't handle table joins or secondary
indexing very well,
There are no foreign keys, however, it seems to handle joins
Got a lot of messages ahead of me and someone may have already
posted this. See the analysis done by Tim GeoCrawler Perdue:
http://www.phpbuilder.com/columns/tim2705.php3?page=1
Tim was one of the guys doing the heavy lifting that brought
Sourceforge.net into being.
ccb
I've been looking into this recently, as I really wanted transaction
support for my database. However, given my web hosting situation, it's
much easier to run MySQL. What follows it what I've researched, but
haven't actually implemented yet.
On Sun, Feb 17, 2002 at 09:39:31PM -0500, Rich
All,
Please don't misunderstand the subject line as flamebait. I have been
dealing with databases a lot more (than I ever wanted to) recently,
and I am trying to figure out the advantages and disadvantages of both
postgresql and mysql. Especially now that I have been doing some web
development,
MySQL is great for small queries and small databases. It's quite a
fast db engine that supports almost all of the Structured Query
Language. It was originally designed to be quick, small, and
flexible, which is exactly where it excels.
PostgreSQL is the descendant of Ingres, which was one
On Sun, 17 Feb 2002 [EMAIL PROTECTED] wrote:
MySQL is great for small queries and small databases.
While I'm no expert in this stuff (indeed, I rarely touch it), my
understanding is that MySQL is great for databases which are mostly
read-only, as opposed to just small. MySQL is optimized for
On Sun, 17 Feb 2002, Benjamin Scott wrote:
On Sun, 17 Feb 2002 [EMAIL PROTECTED] wrote:
MySQL is great for small queries and small databases.
While I'm no expert in this stuff (indeed, I rarely touch it), my
understanding is that MySQL is great for databases which are mostly
read-only,
