Hi, I would not recommend to test against a different database system than the one you really use in your app (eg. your app runs against Postgres and your tests against SQLite in this example) as the behaviours can defer.
Senior Software Engineer at Schwarz IT, focuses on Symfony PHP & React.js at work, makes Apps & Chrome Extensions with TypeScript, React, Svelte and Vue in spare time <https://vikbert.github.io/>
yes, your are absolute right. SQLite will not be able to replace the MysQL or PostgreSQL DB, because of its limited features. It is actually your decision at the end, if this approach is ok for your current project. If you have very complex Datbase queries, which are not possible in SQLite. It is not recommended to use in-momory DB for DB test. But the project has simple DB schema and simple DB queries, then SQLite in-memory-DB will be a lightweight alternative for your DB tests.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi, I would not recommend to test against a different database system than the one you really use in your app (eg. your app runs against Postgres and your tests against SQLite in this example) as the behaviours can defer.
yes, your are absolute right. SQLite will not be able to replace the MysQL or PostgreSQL DB, because of its limited features. It is actually your decision at the end, if this approach is ok for your current project. If you have very complex Datbase queries, which are not possible in SQLite. It is not recommended to use in-momory DB for DB test. But the project has simple DB schema and simple DB queries, then SQLite in-memory-DB will be a lightweight alternative for your DB tests.