fix: allow value type to mismatch with column type #145
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.
Due to SQLite flexibility, we can store text in
INTEGER
fields, but this is currently impossible: when attempting to do so, the value is automatically converted toNULL
.Although this can be quite critical in some contexts, it is supported by SQLite as a 'non-bug'. If you already have fields with mismatched types, it becomes impossible to make any corrections because the value will always be converted to
NULL
. So, even though I'm personally not a big fan of this idea, it cannot be ignored.