separate generator and column defination

[Diluka]

Feature Description

use a value generator not means must use some predefined column types

The Problem

a column using uuid generator does not mean it only stored uuid. uuid just use as a default id strategy, and it prefer assigned id value. and now, mysql driver change uuid type from varchar to char. it break designs

The Solution

separate the options, make @Generated("uuid") is not equal to @Column({type:"uuid"}). just like hibernate-jpa generator is separate from column define.

Considered Alternatives

or define another type uuid2. one is varchar and other is char

Additional Context

• feat: use char(36) for uuid representation in mysql #7853
• breaking change on uuid column #8002

Relevant Database Driver(s)

DB Type	Relevant
aurora-data-api	no
aurora-data-api-pg	no
better-sqlite3	no
cockroachdb	no
cordova	no
expo	no
mongodb	no
mysql	yes
nativescript	no
oracle	no
postgres	no
react-native	no
sap	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.