-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Db record parsing fixes #168
Conversation
fdf6a50
to
12815fa
Compare
12815fa
to
01623e4
Compare
source/modules/database/schema.py
Outdated
"task": "varchar", | ||
"start": "datetime", | ||
"end": "datetime", | ||
"host_locked": "boolean", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sqlite doesn't know boolean, maybe we should call it int?
2.1. Boolean Datatype
SQLite does not have a separate Boolean storage class. Instead, Boolean values are stored as integers 0 (false) and 1 (true).
SQLite recognizes the keywords "TRUE" and "FALSE", as of version 3.23.0 (2018-04-02) but those keywords are really just alternative spellings for the integer literals 1 and 0 respectively.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bools/text are minor comment. I don't see any need to work on that more. Having in mind that we're likely to change approach to callback plugin
Change dict to list translation in DbWrite..write_records Add staticmethod DbWriter.record_with_json
01623e4
to
79c597d
Compare
bugfix 75cf653