Refactor queries: avoid type casts#240
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a small refactoring of the queries in the application and the scripts.
values, defaults to empty arraydb.prepare(from better-sqlite3) to avoid type casts (or rather: let the package do the type cast, there is no runtime check)ASfor all aliases in SQL queries to distinguish them easily (in global searches) from type casts in TypeScript.So instead of
we can write
Here, the first generic allows type checking of the passed arguments to
.all()resp..get(). When no arguments should be passed,never[]is appropriate.