MySQL: TinyInt must be compatible with Int and Boolean scalar types

[mavilein]

Currently we allow TinyInt only to be used on fields of type Boolean. This is problematic for introspection CI and hence we want to lift that restriction and also allow it for Int.

Goal:
The following schema should be valid.

model Blog {
  id    Int     @id
  anInt Int     @db.TinyInt
  aBool Boolean @db.TinyInt
}

SQL Mapping Rules:

• Int @db.TinyInt is mapped to tinyint in the database without display width.
• Boolean @db.TinyInt is mapped to tinyint(1) in the database.

Steps:

• allow this schema in the parser
• adapt introspection engine to adhere to SQL mapping rules
• adapt migration engine to adhere to SQL mapping rules

[do4gr]

The introspection engine will also take the default value into consideration. So column tinyint(1) Default 5 will still be an Int.

[mavilein]

The only outstanding part is the work in the ME.

[FredericEspiau]

This is no longer part of 2.11.0 ?

[mavilein]

The work is done in prisma introspect, the schema parser and the Prisma Client. Only work left is prisma migrate where we will tackle this at a later point.

[tomhoule]

This has been fixed by the native types work.