You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As further testing. I applied the migrations generated, then generated migrations again and it generated the same migrations again. It's clear these migrations are a noop, despite being generated.
Issue description
Postgres geometry column is always being altered to type geometry in every migration despite already being type geometry
Expected Behavior
A geometry column that is not modified should not be included in migrations
Actual Behavior
When performing a migration unrelated to a column that is of type
geometry
, every geometry column I have in my database is included in the migration.For example:
Steps to reproduce
For example:
Create your database with the initial migrations
Alter another table in some way.
See that the migrations include modifying the entity with the geometry type.
For example:
My Environment
Additional Context
No response
Relevant Database Driver(s)
Are you willing to resolve this issue by submitting a Pull Request?
No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.
The text was updated successfully, but these errors were encountered: