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

Would all the stuff in .cogs/ fit into a SQLite database? #126

Open
jamesaoverton opened this issue Jun 10, 2021 · 1 comment
Open

Would all the stuff in .cogs/ fit into a SQLite database? #126

jamesaoverton opened this issue Jun 10, 2021 · 1 comment
Labels
question Further information is requested

Comments

@jamesaoverton
Copy link
Member

Almost everything in .cogs/ is a table. The main exception is formats.json but I think that could fit into a table with two columns: format ID and the format JSON.

Would a cogs.db file be better than a .cogs/ directory? I'm finding myself using multiple Google Sheets for a given project, so I make various subdirectories each with their own COGS setup: foo/.cogs/ and bar/.cogs/. Maybe multiple .db files would be better? cogs foo.db add baz.tsv, cogs foo.db push

Changing over would be a pain, so we'd want a big win, and this doesn't seem big enough.

@jamesaoverton jamesaoverton added the question Further information is requested label Jun 10, 2021
@bjonnh
Copy link
Contributor

bjonnh commented Jun 11, 2021

What would be the advantage of that? Do you have a lot of duplicate information or performance issue?

If not maybe we could just namespace the google sheets and cogs would handle that itself with directories?
For backward compatibility it could still read directly in the .cogs but newly added sheets could be in
.cogs/sheets//…

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

No branches or pull requests

2 participants