Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Investigate whether our gem should store state on disk #4

Open
ethan-readyset opened this issue Nov 2, 2023 · 0 comments
Open

Investigate whether our gem should store state on disk #4

ethan-readyset opened this issue Nov 2, 2023 · 0 comments
Milestone
Milestone 2

Comments

@ethan-readyset
Copy link
Contributor

ethan-readyset commented Nov 2, 2023 •
edited
Loading

As of right now, this is more of a spike. We need to investigate 1) whether our gem needs to store state on disk and 2) what state our gem needs to store. This will depend on whether we want to provide a way for users to change routing decisions for queries at runtime.
@ethan-readyset ethan-readyset modified the milestones: Milestone 1, MVP Nov 2, 2023
@ethan-readyset ethan-readyset changed the title Add sqlite database Investigate whether our gem should store state on disk Nov 22, 2023
@ethan-readyset ethan-readyset removed this from the Milestone 1 milestone Nov 30, 2023
@ethan-readyset ethan-readyset added this to the Milestone 2 milestone Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Milestone 2
Development

No branches or pull requests
1 participant
@ethan-readyset