Do you train Kung Fu?
Or know someone who does?
Then check out KungFuPeople.com
Mobile version of this pageWhen '_properties' gets stuck as a persistent attribute
Next:
ARTWORDSBOOKSHOPQRSTUVWXYZ
Related blogs
PSP - Python Server PagesPostgreSQL, MySQL or SQLite
Creating a user for postgresql
Adding a year in PostgreSQL
Date formatting in python or in PostgreSQL
Integer division in programming languages
Running simple SQL commands on the command line
pg_class to check if table exists
List of casts in PostgreSQL
Just Oracle and IBM?
ALTER TABLE patch
Quick PostgreSQL optimization story
Date formatting in Python or in PostgreSQL (part II)
Sorting transform function in PostgreSQL
To sub-select or not sub-select in PostgreSQL
Speed test between django_mongokit and postgresql_psycopg2
UPPER vs. ILIKE
Fastest "boolean SQL queries" possible with Django
Optimization of getting random rows out of a PostgreSQL in Django
Connecting with psycopg2 without a username and password
Related by category
Linux
Why bother with MySQL...
http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL9th of October 2008
...over PostgreSQL?
I've just read through this document:MySQL vs PostgreSQL and it's obvious paragraph after paragraph that PostgreSQL is the better database. Performance, features and community are all in PostgreSQL's favor. There is almost nothing in MySQL's favor apart from obscure things like faster count(*) (without conditionals) and built in replication support. In the last two weeks I've also had the great fortune of playing with full textindexing in both MySQL and PostgreSQL and again, MySQL sucks ass and PostgreSQL (8.3) is really impressive and fast. (I've used both databases quite extensively over the past 8 years as a web developer)
I once heard that Google uses MySQL for its user database with a custom built transaction machine. And I read that Google engineers had donated some great code to the MySQL project. But why do they bother? What do they know that other engineers don't? And why is MySQL so popular with cheap stack-em-high LAMP hosting sites?
I do understand that PostgreSQL came off a bad start 5 years ago(ish) when it didn't support Windows which meant that newbies had to use MySQL and that stigma is still lingering but that was a very long time ago.
I guess it takes a lot of convincing to switch from one technology to another once you've set your mind on something. That's why we're human. A proof of this is shown if you scroll down to the bottom of this page there's a little simple survey and despite being on a long article with objective convincing arguments that PostgreSQL is better MySQL is doing quite well. Why?
Comment
In general, it is a well-known phenomenon in markets šat good enough easily trumps what is best, if best requires more effort, planning, knowledge or any other number of factors. MySQL, just like Microsoft products, are a pain to use but a breeze to start using, so people usually put up wiž a lot of pain over a lifetime just for fear of reviving some of it by restarting on a better foot. Še network effect takes care of še rest.
About Google, it seems have very different requirements šan common users. For one, šey really do not care about being good free software players; šey often do not release source code, and are known to have used proprietary software out of expediency wižout caring about helping develop free software alternatives.
Put šese two factors togešer, and we get a picture: Google probably started using MySQL just because it made it relatively easy to plug Big Table or Map Reduce under it, and never cared about developing še same interface for PostgreSQL, even if PostgreSQL would benefit še world much more in še long term, just because wiž šeir MySQL familiarity it would have taken longer to do še right žing to reach še market earlier šan prospective rivals.
Google is a company builder, it is not a community builder.
God help me, I put aside a whole afternoon to fugire this out.