Grzegorz Śliwiński

@havok2063 see this line: https://github.com/ClearcodeHQ/pytest-postgresql/blob/main/.github/workflows/tests.yml#L82 It's the github action test where I do connect the tests to the running docker service with postgresql

@havok2063 this fixture is supposed to create a test database for all tests in a module? Do you have tracebacks to the first error?

Still... two years.... Could you migrate and update separately? I mean do one first, and once working, take care of the other? (ie gh actions first, update later or the...

@havok2063 sorry for the sporadic responses, do you have that as open-source? Could I take a look?

@winglian the latest release of https://github.com/ClearcodeHQ/pytest-postgresql/tree/v3 branch got backported support for pytest 7. (3.1.3 - https://pypi.org/project/pytest-postgresql/3.1.3/ ) I'm open to backporting fixes to v3, but won't actively pursue it. Not...

Thanks to you it'll be bit easier to find :)

postgresql_factory is not context manager, it does return connection though. Are you trying to use it as such? What's your use case? ANd what is the full error?

@efagerberg have you tried this approach: https://github.com/ClearcodeHQ/pytest-postgresql#using-a-common-database-initialisation-between-tests ? Maybe I should specifically state, that it also ought to speed up the test initialisation 🤔

@efagerberg that's true, or you'd need at least several schemas within a database. I can see that the noproc fixture factory could be used to create more templates databases for...

Another question, what will the subtransactions be good for if the code you're testing creates its own connections. This would be the best way to use PostgreSQL, you've got a...