Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: DatabaseJanitor Isolation Level #357

Closed
jcpunk opened this issue Jan 11, 2021 · 0 comments · Fixed by #358
Closed

Feature: DatabaseJanitor Isolation Level #357

jcpunk opened this issue Jan 11, 2021 · 0 comments · Fixed by #358

Comments

@jcpunk
Copy link
Contributor

jcpunk commented Jan 11, 2021

What action do you want to perform

It appears that the isolation_level is hard coded to ISOLATION_LEVEL_AUTOCOMMIT. It would be handy if I could alter that for both the DatabaseJanitor class and the postgresql fixture.

What are the results

The database tests with a specific isolation level. My approved database config uses a different isolation level. As a result, my tests are technically different than what I'm running in production.

What are the expected results

A way to tweak the isolation for folks (like myself) with strange requirements.

[1] https://github.com/ClearcodeHQ/pytest-postgresql/blob/master/src/pytest_postgresql/janitor.py#L82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant