Extension 'ltree' already exists. about django-test-migrations HOT 6 CLOSED

But yes, that was it.

The problem stemmed from that first migration that was trying to create the extension twice and by adding the adequate SQL line in the migration that ads the extension fixed it.

Thank you for your help!

from django-test-migrations.

I will be happy to submit a PR if I can figure out how :)

from django-test-migrations.

Looks like for some reason you have ltree extension setup twice.
We don't deal with this (or any other) extensions in this package directly.

I would recommend to check what exactly the state of the database before the test run and what does it actually run.

Does this help you? 🙂

from django-test-migrations.

Yes, I was just investigating this issue and I noticed the initial migration had this line:

schema_editor.execute("CREATE EXTENSION ltree;")

So I can definitely change this to CREATE IF NOT EXIST.

However, what I do not understand is why would this migration run twice for the same database. I guess that at init time the extension creates two databases (or something similar) under the hood to be able to get the old_state and the new_state ?

In any case, making this change seems that it solved the issue, now I am running into other issues, but I think that's on me :)

Let me not close this issue for now so I can investigate this further and leave a good response in this thread as documentation.

from django-test-migrations.

Do you use pytest for regular tests and unittest for this one?

from django-test-migrations.

No, I use pytest as a runner with unittest cases (the DRF unittest anyway, but unittest none the less).

from django-test-migrations.