Change MySQL bool mapping from TINYINT(1) to TINYINT

[paranoiq]

Since 8.0 MySQL throws whis warning "1681 [HY000] Integer display width is deprecated and will be removed in a future release." when integer column with display width is created

This change is backwards compatible and can be merged into all active branches (does not trigger column type update migration)

[derrabus]

Would this break our introspection of boolean columns?

You've also changed the behavior for MariaDB. Was that intended?

[github-actions]

There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.
If you want to continue working on it, please leave a comment.

[Rixafy]

This solves the problem when someone wants to have custom TINYINT, now it's not possible since this always triggers migration, as mentioned in related issue - because it compares TINYINT(1) with custom defined type that doesn't have (1) in it.

Would this break our introspection of boolean columns?

Change does not trigger migration and it's compatible with all MySQL/MariaDB versions, but the definition in newly generated migrations (when adding columns) will be different, it will be declared as TINYINT instead of TINYINT(1), and default value in MySQL/MariaDB is TINYINT(3), but it has no effect on column size, only on width - how many characters to display, for some systems that read those metadata.

You've also changed the behavior for MariaDB. Was that intended?

Since we haven't heard back from the author, I suggest that it's good for all MySQL-based DB, because it makes definition of custom TINYINT type easier.