We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postgres geometry column is always being altered to type geometry in every migration despite already being type geometry
A geometry column that is not modified should not be included in migrations
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.
geometry
For example:
await queryRunner.query(`ALTER TABLE "locations" ALTER COLUMN "coordinate" TYPE geometry`);
import {Point} from "geojson"; @Column("geometry") coordinate!: Point
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.
await queryRunner.query(`ALTER TABLE "some_other_table" ALTER COLUMN "coordinate" TYPE geometry`);
No response
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:
No branches or pull requests
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: