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
I wanted to throw out an idea for PGLite. I want to use it for a bunch of jest tests in our backend application. So far I have a setup that is working nicely. But... it takes roughly ~1-2 seconds to push my schema into the DB with Drizzle and than seed it with base data that is used in a ton of our tests.
It would be really awesome if I could set up a PGLite DB at the beginning of our test runs in something akin to globalSetup in jest, where I establish the DB and seed it with data, than pass that instance to all the suites. In the before all for each of the suites, they would call this duplicate method on the DB. This way each suite wouldn't have the pay the "start up" cost of getting the DB ready to run against.
The text was updated successfully, but these errors were encountered:
Scalahansolo
changed the title
[Feature Request] duplicate method
[Feature Request] duplicate method to copy a PGLite DB into a new DB
Nov 7, 2024
I wanted to throw out an idea for PGLite. I want to use it for a bunch of jest tests in our backend application. So far I have a setup that is working nicely. But... it takes roughly ~1-2 seconds to push my schema into the DB with Drizzle and than seed it with base data that is used in a ton of our tests.
It would be really awesome if I could set up a PGLite DB at the beginning of our test runs in something akin to
globalSetup
in jest, where I establish the DB and seed it with data, than pass that instance to all the suites. In the before all for each of the suites, they would call thisduplicate
method on the DB. This way each suite wouldn't have the pay the "start up" cost of getting the DB ready to run against.The text was updated successfully, but these errors were encountered: