Re: Database Preference?
| From: | Miles Thompson | Date: | Wed, 29 Aug 2001 10:30:45 +0000 |
| Subject: | Re: Database Preference? | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-64980@lists.php.net to get a copy of this message | ||
If you are used to Informix, MySQL will be unsatisfying - no stored procedures, outer joins, sub-queries, transactions. MySQL is much like early dBase II.
I'm not familiar with MS SQL on a price per seat basis, but how many developers do you have? If you are doing this web-based you don't have that many "seats". Given that your developers are used to working in MS SQL it may be cheaper in terms of overall developer costs.
The downside of that course is that you are locked into MSFT's plans for the product and Windows NT/2000/XP.
A robust and reliable open source alternative is PostgreSQL. It has features your developers are used to, is adequately fast, and is certainly robust. It would probably be the easiest port. Drivers are kept current in PHP, Python, Perl and of course ODBC.
Regards - Miles Thompson
At 09:50 PM 8/28/01 -0400, james wrote:
We have several GUI applications that we are preparing to convert to web-based applications, based primarily on PHP. The applications are based on Informix On-Line (on a SCO Unix server) and MS SQL (on NT). Since we will be doing a port, in any case, I am wondering your thoughts on whether MySQL may be a better database solution. This is particularly important from a price-performance point of view since the other two databases are quite pricy on a per-seat basis. TIA, James -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net For additional commands, e-mail: php-general-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net