Import pre-migration data from an SQL file about django-test-migrations HOT 3 CLOSED

For that case django already supports test fixtures, but now as I write this, I am kinda confused: in which state a test-fixture would be applied at? surely it should be the before-state right?

It should be applied after calling .before()(example) or inside .prepare() when using unittest testcase (example), because .before() goal is to prepare database state without migration that is being tested applied, so you can populate all necessary data to test this migration.

Generally you can do whatever you want there, even load execute some raw SQL queries, however please remember that tables scheme can change, so you will have to version somehow your SQL files and solve some other challenges related to maintaining SQL files.

from django-test-migrations.

Hello @vesnikos

What do you mean by "sql extract"? SQL EXTRACT function or just executing some raw SQL queries?
Generally you can do whatever you want in .prepare() to setup some test data for instance, you can execute raw SQL queries like in your example

from django-test-migrations.

HI @skarzi ,

Yes, sorry. by extract I was refering to a partial data-only dump from the database before any migrations. That .sql file over there, was just containing a bunch of import statments generated from our live database.

If that's the case and could be done, it would be great there was a reference of such use case in the documentation.

Using file-fixtures to populate the table makes sense if you have multiple tables and inputing mock data is cumbersome. For that case django already supports test fixtures, but now as I write this, I am kinda confused: in which state a test-fixture would be applied at? surely it should be the before-state right?

from django-test-migrations.