If there is a schema mismatch between when query!()'s checks were run and when the query is actually executed, we can have unexpected (but still technically safe) behavior in most of our Decode impls due to various assumptions (#7).
Since Postgres and MySQL both report to us the data types in the result, we should check that the type we've been asked to decode matches via <DB as HasSqlType<T>>::metadata().
If there is a schema mismatch between when
query!()'s checks were run and when the query is actually executed, we can have unexpected (but still technically safe) behavior in most of ourDecodeimpls due to various assumptions (#7).Since Postgres and MySQL both report to us the data types in the result, we should check that the type we've been asked to decode matches via
<DB as HasSqlType<T>>::metadata().