Write MySQL & Postgres Enum Columns

[billy1624]

PR Info

• Required by Codegen ActiveEnum & Create Enum From ActiveEnum sea-orm#348
• Depends on
  • Add TableRef::DatabaseSchemaTable sea-query#193
  • Write database & schema prefix in TableRef for all databases sea-query#202

[tyt2y3]

I don't actually understand why this is necessary. But certainly does not seem right.
Because in the general case, there are database > schema.
Which means we either add DatabaseSchemaTable or simply use SchemaTable as is.

[billy1624]

I don't actually understand why this is necessary.

It's needed because the "schema prefix" will be and should be ignored by MySQL & SQLite

• Behaviour changed on sea-query since SeaQL/sea-query@27d0150
• Mainly supporting this line in sea-orm

But certainly does not seem right. Because in the general case, there are database > schema. Which means we either add DatabaseSchemaTable or simply use SchemaTable as is.

I will go with DatabaseSchemaTable and dropping the DatabaseTable that I proposed in this PR

• For Postgres, it will construct SQL statement with "database"."schema"."table"
• For MySQL & SQLite, it will construct SQL statement with "database"."table" (ignoring the supplied schema)

How is that sounds? @tyt2y3

[billy1624]

Hey @tyt2y3, DatabaseSchemaTable was added on SeaQL/sea-query@1ff761d

[tyt2y3]

We might want to wait for the next 'train' of sea-query release

[billy1624]

Yes, but we can merge this into master first without release a new version of sea-schema now

[tyt2y3]

Please release sea-query and remove this

[tyt2y3]

Please release sea-schema as well