Null values in SQLite are being converted to default values without error or default attribute about sqlx HOT 2 OPEN

This is actually a well defined type conversion according to SQLite (scroll down for the conversion table): https://www.sqlite.org/c3ref/column_blob.html

Normally, we don't explicitly implement type conversions, because that should be handled in the database itself. For the MySQL or Postgres driver, this would be an error. However, since the SQLite API functions implement this conversion internally, it's actually more work for us to prevent the conversion, so it was just omitted.

If you use the checked Row::get() or ::try_get() methods, this will panic or error, respectively, but the FromRow derive uses ::try_get_unchecked() to avoid an extra branch on decoding the value. This also allows conversion between types that are binary-compatible but not considered compatible in the API.

I'm not particularly married to any of these decisions, but there's a high likelihood that there are people out there who depend on the current behavior.

from sqlx.

Oof, fair enough. I didn’t know this was inherent behavior of SQLite, and I think it really caught me off guard since the behavior is a significant departure from how most other Rust deserializations I have used work and figured since the SQLx macros disallowed the mismatch it was an unintended inconsistency.

I’m not going to fight to have this changed though I might ask that the docs are updated to specifically note that FromRow derivations when using SQLite will not Err if a NULL value on a required field is encountered. That would be helpful, I got spun around on this for a few hours.

Thanks for explaining what was going on so well.

from sqlx.