Any reason for deprecation of connect/disconnect?

Hey @Warren Day 👋 The reason was to allow having models of the same name, so from now you would need to use

prisma.$disconnect

instead. Just adding a

$

in front. Same goes for

trasnaction

You can read more about this in the release notes of the

2.4.0

release: https://github.com/prisma/prisma/releases/tag/2.4.0

I guess thats true for all top level methods, given the API structure. Thanks for confirming 🙂

Just to make sure: Did you get an error message where it did not just tell you what to use instead?