Postgres geometry column is always being altered to type geometry in every migration despite already being type geometry

[jcapogna]

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:

await queryRunner.query(`ALTER TABLE "locations" ALTER COLUMN "coordinate" TYPE geometry`);

Steps to reproduce

1. Create an entity with a column of type geometry.

For example:

import {Point} from "geojson";

@Column("geometry")
coordinate!: Point

2. Create your database with the initial migrations

3. Alter another table in some way.

4. See that the migrations include modifying the entity with the geometry type.

For example:

await queryRunner.query(`ALTER TABLE "some_other_table" ALTER COLUMN "coordinate" TYPE geometry`);

My Environment

Dependency	Version
Operating System	OSX
Node.js version	20.11.0
Typescript version	5.4.2
TypeORM version	0.3.20

Additional Context

No response

Relevant Database Driver(s)

• [ ] aurora-mysql
• [ ] aurora-postgres
• [ ] better-sqlite3
• [ ] cockroachdb
• [ ] cordova
• [ ] expo
• [ ] mongodb
• [ ] mysql
• [ ] nativescript
• [ ] oracle
• [X] postgres
• [ ] react-native
• [ ] sap
• [ ] spanner
• [ ] sqlite
• [ ] sqlite-abstract
• [ ] sqljs
• [ ] sqlserver

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.

[jcapogna]

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.