Try to parse u32 in PG as i32 if Oid fails #2753
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug Fixes
Currently, trying to parse u32 from an INT column in Postgres fails with
Err value: DBError(Query(SqlxError(ColumnDecode { index: "\"number\"", source: "mismatched types; Rust type core::option::Option<sqlx_postgres::types::oid::Oid> (as SQL type OID) is not compatible with SQL type INT4" })))
This change adds a fallback - if parsing to Oid fails, try parsing as i32.