Skip to content

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

Description

@jamesaoverton

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.

Activity

  1. bjonnh commented on Jun 11, 2021

    @bjonnh
    Contributor

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions