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.

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

Avoid the centralized store #6

Closed
wlandau opened this issue Mar 29, 2020 · 5 comments
Closed

Avoid the centralized store #6

wlandau opened this issue Mar 29, 2020 · 5 comments

Comments

@wlandau
Copy link
Collaborator

wlandau commented Mar 29, 2020

Use qs on individual targets

@wlandau
Copy link
Collaborator Author

wlandau commented Mar 29, 2020

Should live in targets/data inside the project.

@wlandau
Copy link
Collaborator Author

wlandau commented Mar 30, 2020

I am stuck on how to deal with formats. Should we use file extensions to indicate the format? With extensions, we risk saving duplicate files, and we need to specify the format just to read the object. This is what is in 334e3f1, but it is not ideal because it breaks the data abstraction we want. The alternative is to save the target with no indication about the format, but that leaves us wondering what format to use when we go to read the target.

@wlandau
Copy link
Collaborator Author

wlandau commented Mar 30, 2020

Metadata should have the format. For now, let's use the _data suffix to indicate methods that only deal with the data values. In practice, we will setting values will be non-blocking and threadsafe, while metadata manipulation will always be a blocking operation because the metadata will be centralized (in an RSQLite database?).

@wlandau
Copy link
Collaborator Author

wlandau commented Mar 30, 2020

Sketched out the basics. Need #5 next.

@wlandau wlandau changed the title Low-tech data store Avoid the centralized store Mar 31, 2020
@wlandau
Copy link
Collaborator Author

wlandau commented Mar 31, 2020

Avoid the centralized data store. Use metadata as the centralized class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant