• qaz@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    1 day ago

    It’s used to export tracking data to analyze later on. Something like SQLite seems like a much better choice to me.

    • expr@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      5 hours ago

      If it’s an export that will be consumed by a separate, unrelated program later, I think a CSV is most appropriate. Databases are persistence tools, not transport.

      • qaz@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        It’s only intended to be used by the program itself. It’s purely storage.

        • expr@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          2 hours ago

          Ah so it’s not really an export, it’s just the backing store used by some other (locally-running) program that you’re trying to reverse engineer?

          In that case yeah an sqlite database is probably most appropriate, though I can see a CSV still being desirable to remove a potential sqlite dependency.