Tuesday, March 4, 2008

More RDBMS incompatibilities!

Oh shi-

I just noticed that MySQL's string comparisons are by default case insensitive, while PostgreSQL has case sensitivity. MySQL's behavior can be changed by collations, while PostgreSQL doesn't support that. So, to make PostgreSQL case insensitive with CPU-intensive comparisons, or to make MySQL case sensitive, probably making a mess of the portability on the same go - that is the question. Oh, I haven't dared to check out SQLite yet.

From the quite limited experience I've had with the more specific differences between the two major SQL engines, I'm calling it a tie for now. PostgreSQL really tries to be a solid champion, I'd imagine it aspires to be a free version of Oracle, but some implementations might limp a bit. MySQL on the other hand wants to be the hip and pop engine, that does everything and is really proud of the spotlights its getting. It's actually so fascinated by itself that corner cutting is always an option, because it knows that everyone will love it nonetheless.

PS: I haven't done much actual coding tonight, due to the Wikipedia-effect I get when searching for stuff I need to take into consideration. Here, catch!

No comments: