[aurora-data-api] Using unsigned int columns causes FK drop / recreation

[mkilp]

Issue Description

Default width of unsigned columns of unsigned columns does not match metadata in MariaDB and MySQL 5.7. This also applies to Aurora MySQL. A fix has been implemented in #6632 for MySQL but never replicated into aurora-data-api.

Opening this issue for tracking and testing. PR follows.

Expected Behavior

Metadata of an INT UNSIGNED column is detected with a width of 10. Migrations should not detect this as a changed column.

Actual Behavior

Metadata of an INT UNSIGNED column is detected with a width of 11. This causes migrations / synchronize to recreate the column over and over again. All foreign keys pointing to these columns are recreated.

Steps to Reproduce

Create an entity with

@PrimaryGeneratedColumn({ unsigned: true })
      id: number;

and have synchronize on. The column will be changed every time.

My Environment

Dependency	Version
Operating System	Windows 10
Node.js version	16.14.2
Typescript version	4.6.2
TypeORM version	0.3.10

Additional Context

Fix is found, PR follows.

Relevant Database Driver(s)

DB Type	Reproducible
aurora-mysql	yes
aurora-postgres	no
better-sqlite3	no
cockroachdb	no
cordova	no
expo	no
mongodb	no
mysql	no
nativescript	no
oracle	no
postgres	no
react-native	no
sap	no
spanner	no
sqlite	no
sqlite-abstract	no
sqljs	no
sqlserver	no

Are you willing to resolve this issue by submitting a Pull Request?

• ✅ Yes, I have the time, and I know how to start.
• ✖️ Yes, I have the time, but I don't know how to start. I would need guidance.
• ✖️ No, I don’t have the time, but I can support (using donations) development.
• ✖️ No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.