UUID Fields not handled properly for MySQL backend.

[farzbood]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the SQLModel documentation, with the integrated search.
• I already searched in Google "How to X in SQLModel" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to SQLModel but to Pydantic.
• I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

• I commit to help with one of those options 👆

Example Code

The SQLModel docs. code example:
https://sqlmodel.tiangolo.com/advanced/uuid/?h=uuid#__tabbed_1_1

Description

Hi everyone,

Just run the code example from the docs.
SQLModel creates a Char(32) column for the UUID type Fields, when used by MySQL backend, however the appropriate size would be Char(36) as mentioned in almost every known source about UUID (as of in fastapi-users handled).
The problem is, when having Tables that supposed to have Relations (FKs) with other Tables having UUID as PK.
e.g: having a Contacts Table with a FK relates to User.id in fastapi-users.
Is there a straight forward way to handle such scenario with SQLModel to create an appropriate Field with desired Type and Size: Char/VarChar(36), or have to write custom code to handle the case?

P.S
If the FK define as str (as suggested in SQLModel Docs. to create a VarChar(n) it conflicts when using PostgreSQL as backend that used uuid type internally and could not establish FK with str type)

Operating System

Windows

Operating System Details

No response

SQLModel Version

0.0.24

Python Version

3.10.16

Additional Context

No response