Re: MySQL vs. PostgresSQL
- From: "Linn Kubler" <lkubler@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Sep 2008 17:02:22 -0500
A few years ago I worked on a project that had PostgreSQL as the backend, I
found it to be a very good database to work with, liked it quite a bit
actually. A few years after that I wanted to see what all the hubbub was
with MySQL and did some research and played just a little bit. While it
seemed like a good system I found it was missing some features that
PostgreSQL had so I concluded I preferred PostgreSQL.
Today I'm working with SQL Server from Microsoft so I've sort of lost touch
with the open source products so I can't even recall what features MySQL
were missing. But if I wanted to go back I'd still go with PostgreSQL.
Just my 2 cents worth. But I also agree with Olaf, you really need to
define what you need the database to do before you can select one
appropriately.
Thanks,
Linn
"Rush Strong" <rush.strong@[DELETEME]verizon.net> wrote in message
news:%23GmfwLqFJHA.4056@xxxxxxxxxxxxxxxxxxxxxxx
My client is in the process of revamping their system, and wants to use a
Linux/SQL backend. Can anyone give me advice on MySQL vs. PostgreSQL? We
plan to use it primarily for data storage, with the business rules in VFP.
Thanks -
- Rush
.
- References:
- MySQL vs. PostgresSQL
- From: Rush Strong
- MySQL vs. PostgresSQL
- Prev by Date: Re: moving corporate database out of vfp
- Next by Date: Re: MySQL vs. PostgresSQL
- Previous by thread: Re: MySQL vs. PostgresSQL
- Next by thread: Re: MySQL vs. PostgresSQL
- Index(es):
Relevant Pages
|