Opened 4 years ago
Closed 4 years ago
#32487 closed Bug (wontfix)
GIN indexes on Postgres doesn't work with --nomigrations
| Reported by: | Iuri de Silvio | Owned by: | Iuri de Silvio |
|---|---|---|---|
| Component: | Migrations | Version: | 3.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I want to test with --nomigrations for performance reasons, but I have a GIN index and it fails because it doesn't execute a CREATE EXTENSION btree_gin.
Change History (3)
comment:1 by , 4 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 4 years ago
comment:3 by , 4 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
I also agree that this shouldn't be handled by Django by default.
Note:
See TracTickets
for help on using tickets.
I fixed my issue creating the extension on
pre_migratesignal. I think it is a reasonable solution to decouple extension setup and index creation.I tried some solutions with Django internals but they're not good. Signal works for me and after some investigation I don't think it should be handled by Django.