1 min read
Using an SQLite database for testing might come in handy.
Why should we use a database increasing the footprint of a test suite when executing very few queries?
Even few queries are not prepared the same way depending on the database engine and as a result there is no guarantee of having the same records set returned by SQLite and another database used in production.
For instance, I've encountered the following issues before:
- Sorting by date might not work out of the box with SQLite (when not using date functions) as there is no date and time Datatype
- Having a
#character in a query would return an
Unrecognized Tokenerror with SQLite, hence could not precede a comment as it could with MySQL