this post was submitted on 04 Jul 2025
192 points (100.0% liked)

Programmer Humor

24857 readers
967 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 4 days ago (1 children)

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.

[–] [email protected] 1 points 4 days ago (1 children)

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

[–] [email protected] 2 points 4 days 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.