> To clearify, we need to encourage the PHP developer community to > encourage the PHP user community to switch to PostgreSQL. > > What I'm worried about is exactly the people who adopted MySQL already. > The change to another database will be painfull no matter what. How many > of them will be willing to give another open source database a shot?
If you assume that cost is one of the factors in going with an open source database, what are their choices? I know it took me a while to convince the CIO on the project I'm working on that PostgreSQL was an improvement over MySQL. He's slowly coming around as I start to show him what I am doing with the much richer PostgreSQL feature set, but the performance of 7.3 compared to MySQL is likely to remain a bit of a sticking point, because some queries are taking 2-3 times as long on the same platform with the same data. If the data entry folks, who are probably about to get a look at a portion of the application that is still using the MySQL engine, get used to the search times there, when we switch the whole thing over to PostgreSQL we may get complaints if searches that used to take 3-4 seconds are now taking 10-12 seconds. (Have others noticed that 7 seconds seems to be a threshold point for users reacting to query times?) MySQL also does case independent text comparisions, and apparently ONLY case-insensitive comparisons. -- Mike Nolan ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
