Commit 742510b
fix(linux): MySQL information_schema VARBINARY decode + tinyint(1) test
list_tables and fetch_columns on MySQL 8 fail with
"mismatched types; Rust type alloc::string::String (as SQL type
VARCHAR) is not compatible with SQL type VARBINARY" because
information_schema columns come back as VARBINARY in some setups.
CAST every column to CHAR so sqlx decodes them as String.
The value_roundtrip_all_types test asserted Int(1) for tinyint(1)
but sqlx-mysql treats tinyint(1) as a Bool and our extract_value
falls through to the BOOLEAN arm. Accept either Bool(true) or
Int(1) — both are valid representations.
Spotted via failing GitHub Actions runs since the start of the
sprint; Postgres and unit tests were always green.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent bd6b955 commit 742510b
2 files changed
Lines changed: 5 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
61 | | - | |
| 61 | + | |
62 | 62 | | |
63 | 63 | | |
64 | 64 | | |
| |||
77 | 77 | | |
78 | 78 | | |
79 | 79 | | |
80 | | - | |
| 80 | + | |
| 81 | + | |
81 | 82 | | |
82 | 83 | | |
83 | 84 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
144 | 144 | | |
145 | 145 | | |
146 | 146 | | |
| 147 | + | |
147 | 148 | | |
148 | | - | |
| 149 | + | |
149 | 150 | | |
150 | 151 | | |
151 | 152 | | |
| |||
0 commit comments