Fix crashes if the query has undefined as value #707
Closed
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.
Hi!
For example, I have lines like these
noteId
may beundefined
at some points in time. I understand that this is bad and I fixed it, but in this case I get an unpleasant crash.Fetching from the database itself works well with
undefined
, but when you change any record in this table, the application dies. The action is in one place, but the error is thrown from another place. This moment is hard to find and debug.Therefore, I propose to do the same behavior for the fetch and for observe, removing the throwing error.
For example, in the sqlite adapter,
undefined
is set to null. And on observe, undefined == null // => true