-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add database models #289
Add database models #289
Conversation
Co-authored-by: Andrew Plaza <[email protected]>
user_address TEXT PRIMARY KEY NOT NULL, | ||
created_at BIGINT NOT NULL, | ||
last_refreshed BIGINT NOT NULL | ||
user_address TEXT PRIMARY KEY NOT NULL, |
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.
are we re-using some of the tables from XMTP?
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.
This schema below is all we have a need for at the moment. Because OpenMLS has its own database structure with the KeyValue store, some of the tables from the old xmtp
schema simply aren't necessary.
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.
LGTM
Summary
Notes
I decided to break up the DB models into multiple files. The
xmtp
crate'sEncryptedMessageStore
was getting pretty long and unwieldy, especially for tests. I figure we can break up theimpl
blocks for the store methods and all the Trait implementations into the respective per-table files and things should be more manageable. Lmk what you all think.