Database may not be restoring?

Not sure if I’m missing something here but:

const inMemoryDb = newDb();
inMemoryDb.public.none(fs.readFileSync('src/graphql/DB/pgMem/migrations/001-initial.sql', 'utf8'));
const backup = inMemoryDb.backup();
export { inMemoryDb, backup };

When I run this at the top of every test, it doesn’t seem like it’s resetting the DB to the initial migration because in 001-initial.sql I do not seed any “Crafters” for the Crafter table. No crafters were created in 001-initial.sql’. My tests create crafters.

But when I run my tests, it’s not clearing crafters that were created after each test runs it seems. If I output select * from crafters, it seems to be aggregating them.

beforeEach(() => {
  backup.restore();
});

My tests are mainly mocha. A few are test. Right now I’m just talking about the ones using mocha.

[oguimbal]

pg-mem is being supported.

You’ve got some nerve saying that @dschinkel .

I’ve answerered most all of your numerous pseudo-issues, even if most of them were unrelated to pg-mem.

… Then you started sending me 5 emails per day on my personal address (still mostly unrelated to pg-mem), which were sometimes aggressive (depending on the hour they were sent).

So yes, after spending hours trying to answer you at first (and free of charge !), I began to take “some time” to answer.

I’m supporting pg-mem on my free time, so if you want professional support @dschinkel, I would suggest a meaningful donation. I usually charge 300$/hr, and I think I lost at least a day answering your questions and adding the features you asked for. So do the math, and donate, before casually telling that pg-mem is not being supported.

[dschinkel]

I’m done with this. Especially due to your last reply. Good luck in 2022 👋.