You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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//…
Almost everything in
.cogs/
is a table. The main exception isformats.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/
andbar/.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.
The text was updated successfully, but these errors were encountered: