fix(mysql): use column_type for data_type so tinyint(1) detects as bool

`information_schema.columns.data_type` strips length / precision —
returns `tinyint` for both `tinyint(1)` and `tinyint(4)`, collapsing
MySQL's idiomatic boolean type into a generic int. The result was
the bool-checkbox cell editor emitting `"true"` / `"false"` to a
column the parser had classified as `Int`, producing a stray
"Invalid integer" toast on every check.

`column_type` is the canonical column carrying what the user
actually typed (`tinyint(1)`, `varchar(255)`, `decimal(10,2)`,
`enum('a','b')`). Switching the introspection query to it fixes
the bool detection and also gives the Structure tab the
length / precision the user expects to see.

Author: datlechin

linux/crates/drivers/mysql/src/lib.rs

@@ -76,8 +76,16 @@ impl Connection for MysqlConnection {
     }
 
     async fn fetch_columns(&self, schema: Option<&str>, table: &str) -> Result<Vec<ColumnInfo>, DriverError> {
+        // `column_type` is canonical: it carries the precision /
+        // length the user typed (`tinyint(1)`, `varchar(255)`,
+        // `decimal(10,2)`, `enum('a','b')`). `data_type` strips all
+        // that — returns `tinyint` for both `tinyint(1)` and
+        // `tinyint(4)`, which collapses MySQL's idiomatic boolean
+        // type into a generic int and breaks the bool-detection
+        // heuristic in `classify_type`. Prefer column_type for the
+        // displayed `data_type`.
         let rows = sqlx::query(
-            "SELECT CAST(column_name AS CHAR), CAST(data_type AS CHAR),
+            "SELECT CAST(column_name AS CHAR), CAST(column_type AS CHAR),
                     CAST(is_nullable AS CHAR), CAST(column_key AS CHAR),
                     CAST(extra AS CHAR), CAST(column_default AS CHAR),
                     CAST(generation_expression AS CHAR)