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.
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.
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.
It’s only intended to be used by the program itself. It’s purely storage.
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.