-
Notifications
You must be signed in to change notification settings - Fork 24
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
Sqlite store impl #287
base: main
Are you sure you want to change the base?
Sqlite store impl #287
Conversation
I would guess |
Not at all, quite the opposite! These are files that you generate with |
Just saying that the official sqlx repo also has it gitignored. Instead, this should probably be generated and checked in CI. |
presage-store-sqlite/presage.sqlite
Outdated
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.
I think this should also be gitignored. As well as the top-level presage.sqlite
.
presage-store-sqlite/src/protocol.rs
Outdated
let device_id: u32 = address.device_id().into(); | ||
let record_data = record.serialize()?; | ||
query!( | ||
"INSERT INTO sessions ( address, device_id, identity, record ) VALUES ( $1, $2, $3, $4 )", |
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.
As far as I can see, sessions should also be replaced when they already exist (looking at WF).
The same probably also for the various types of keys.
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.
Can you give it another look when it's not a draft anymore?
I plan on double checking constraints on tables themselves, and most tables already have PRIMARY KEY(...) ON CONFLICT REPLACE
.
c7dc705
to
59cee93
Compare
59cee93
to
22a5497
Compare
No description provided.