Skip to content

No way to specify the database for fixtures #1192

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.

Sign up for GitHub

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

Jump to bottom
Open
xi opened this issue Apr 14, 2025 · 3 comments · May be fixed by #1193
Open

No way to specify the database for fixtures #1192

xi opened this issue Apr 14, 2025 · 3 comments · May be fixed by #1193

Comments

@xi
Copy link

xi commented Apr 14, 2025 •
edited
Loading

The only way to declare that a fixture requires a database is the db fixture. However, since #1186 this will only pull in the default database. As far as I can see, there is currently no way to specify a different database.

Prior to #1186, the db fixture pulled in all databases.
xi added a commit to xi/pytest-django that referenced this issue Apr 14, 2025
@xi
Fix regression: pull in all databases instead of default database
98e1628 
fixes pytest-dev#1192
@xi xi linked a pull request Apr 14, 2025 that will close this issue
Open
xi added a commit to xi/pytest-django that referenced this issue Apr 14, 2025
@xi
Fix regression: pull in all databases instead of default database
dc8aa0d 
fixes pytest-dev#1192
@bluetech
Copy link
Member

Please https://pytest-django.readthedocs.io/en/latest/database.html#tests-requiring-multiple-databases. Does that work?

@xi
Copy link
Author

xi commented Apr 15, 2025

@pytest.mark.django_db cannot be used for fixtures, so it does not apply here. The only way to declare that a fixture requires a database is the db fixture, and that does not take any parameters.

@terencehonles
Copy link

I'm also running into this issue.

I was hoping not to auto mark all tests as using a DB and instead let the fixtures pull in a database as needed. This is not something that can be easily configured per fixture, but maybe returning the default set of DBs to pull in via a fixture would allow some customization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix regression: pull in all databases instead of default database xi/pytest-django
3 participants
@xi @terencehonles @bluetech