Testing: compatibility with -no-migrations mode

[benjaminrigaud]

When running pytest --no-migrations, Models are synced to their corresponding tables as-is: no migrations are executed.

django-db-views doesn't support this mode: the views are not created and the tests fail.

As a workaround, I have implemented a fixture to be able to apply any migration on the fly.

A proper implementation in django-db-views could be to uncouple the SQL creating the views from the migration framework: it would permit the creation of a few helper to execute this SQL outside of the migrations (django-pgtrigger does something like that).

What are your thoughts?

References:

• https://pytest-django.readthedocs.io/en/latest/database.html#no-migrations-disable-django-migrations
• https://django-pgtrigger.readthedocs.io/en/4.6.0/faq.html#how-do-i-test-triggers

[BezBartek]

@benjaminrigaud Thank you for your thoughts I will try to get deeper into it through the weekend

[benjaminrigaud]

Hi,

If I implement a fix, would you have time to review it? :bow:

Ben

[BezBartek]

Hello @benjaminrigaud Please do so, thank you! Apologize that I didn't find time to write it I will review your code and merge

[lajus]

Hello,

I have run into the same issue while experimenting with django-db-views on my project.

@benjaminrigaud you said

As a workaround, I have implemented a fixture to be able to apply any migration on the fly.

would it be possible for you to share the code of your fixture ?

Thanks, Jonathan

[benjaminrigaud]

would it be possible for you to share the code of your fixture ?

Sorry @lajus, I can't share that code from a private Repo.

Some details:

• It uses __import__ to import the migration module
• Then instantiates the Migration class from this module
• Then it calls migration.apply(...)