3 ms·
We started with MySQL and switched to PostgreSQL when some unit tests started to fail after doing a minor MySQL upgrade. Something like going from 5.0.1 to 5.0.
by st3fan 19y ago
We started with MySQL and switched to PostgreSQL when some unit tests started to fail after doing a minor MySQL upgrade. Something like going from 5.0.1 to 5.0.2. We tracked this down to MySQL giving completely different result sets for the same (not very complex) query after the small upgrade.
We never looked back. PostgreSQL is really powerful and we use it in a clustered and soon sharded setup. Works well for us.
- immad 19y agoHow is PostgreSQL clustering going? I heard that was a pain, whats your setup?
- st3fan 19y agoSlony. It is far from perfect though. But at least it is a good and stable way to have a backup database ready.
- pyroman 19y agoThat's crazy that there were changes to query results from such a minor revision. I haven't experienced anything like that, but maybe my unit testing could be better.
- babul 19y agoWhat did you use and how were you doing the unit tests (e.g. tools/processes). Thanks.
- st3fan 19y agoSimple JUnit tests for a Repository style class that does database interaction. I can't remember the exact query or details anymore. Just that we were extremely surprised to see that switching back and forth between minor releases gave different results.