SitePoint.com

ArticleBot · Sep 9, 2004, 00:26

This is an article discussion thread for discussing the SitePoint article, "Migrate your site from MySQL to PostgreSQL -- Part 1"

Gator99 · Sep 23, 2004, 11:47

It's the old 90/10 theory. 90% of db apps use 10% of the functionality available. Mysql is a streamlined rdbms that offers greater performance by focusing on this 10%. You shouldn't just switch to postgress because you "heard it was more compliant", you should only make the switch if you really need any of the functionality that mysql does not offer and are willing to trade off performance for this. In many instances you can handle these non-supported features through coding, which will maintain the performance of your application, and eliminate the need to "throw the baby out with the bathwater".

Sep 9, 2004, 00:26	#1
ArticleBot SitePoint Articles Join Date: Apr 2001 Posts: 0	Article Discussion This is an article discussion thread for discussing the SitePoint article, "Migrate your site from MySQL to PostgreSQL -- Part 1"

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

Sep 23, 2004, 11:47	#2
Gator99 Non-Member Join Date: Sep 2004 Location: Florida Posts: 644	It's the old 90/10 theory. 90% of db apps use 10% of the functionality available. Mysql is a streamlined rdbms that offers greater performance by focusing on this 10%. You shouldn't just switch to postgress because you "heard it was more compliant", you should only make the switch if you really need any of the functionality that mysql does not offer and are willing to trade off performance for this. In many instances you can handle these non-supported features through coding, which will maintain the performance of your application, and eliminate the need to "throw the baby out with the bathwater".