You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the amazing library. Your effort has enabled uncountable amazing products to be build that are faster than without this library.
For integration testing I would like to open an existing database file in memory mode, so that further changes are not persisted. Is such a thing possible?
sqlite(process.env.database,{memory: true}),
gives me the error TypeError: Option "memory" was removed in v7.0.0 (use ":memory:" filename instead)
I can use the :memory: file string but then all migrations and seeders need to be re-run which slows down the tests considerably.
I also tried test.sqlite3?mode=memory&cache=shared but this just creates a db with the connection string as name.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Dear better-sqlite3 contributors,
Thank you for the amazing library. Your effort has enabled uncountable amazing products to be build that are faster than without this library.
For integration testing I would like to open an existing database file in memory mode, so that further changes are not persisted. Is such a thing possible?
gives me the error
TypeError: Option "memory" was removed in v7.0.0 (use ":memory:" filename instead)
I can use the
:memory:
file string but then all migrations and seeders need to be re-run which slows down the tests considerably.I also tried
test.sqlite3?mode=memory&cache=shared
but this just creates a db with the connection string as name.The text was updated successfully, but these errors were encountered: