4 ms·
Agreed, and having some experience with both MySQL and SQLite, running SQLite in testing cannot cover problems you'd find with MySQL (e.g. SQLite is so limited
by shlomi-noach 9y ago
Agreed, and having some experience with both MySQL and SQLite, running SQLite in testing cannot cover problems you'd find with MySQL (e.g. SQLite is so limited with concurrency that you cannot use it to confirm concurrency issues will be dealt with in your production MySQL). I would assume the same holds for SQLite<->PostgreSQL.
- _rami_ 9y agoSure, there are often problems differing between the databses. Our Travis CI configuration runs our test suite against all three different databases: https://travis-ci.org/pretix/pretix/builds/351704035 https://travis-ci.org/pretix/pretix/builds/351704035 However, having SQLite at hand for local development/testing makes things easier. In my experience, real-world concurrency issues (that you are talking about) are always hard to find in manual/automated testing, or do you have a good strategy of trying that?
- shlomi-noach 9y ago> In my experience, real-world concurrency issues (that you are talking about) are always hard to find in manual/automated testing I agree, and I don't have a good, generic, strategy for that. I didn't give the best example.