Hello.

I am interested to hear your thoughts on which format you prefer downloading databases/leaks/data in.

I often find myself working with JSON when I run web scrapers, and when I write tools for transforming and processing data sets, I tend to use JSON too.

When possible CSV tends to be much cleaner, and especially smaller. If it's a lot of nested json then its understandable to leave it as is since a lot of people do a bad job converting nested json over to csv.

depends on the usage after that ...

json for importing to OpenRefine or similar interpretations :)

but i think 90% of the users if its not csv,,,, it never happened...
csv for more simple exports .....



insert puke icon here

I like "beautified JSON"

I'll take it how I can get it. Honestly, I just dump the sqls into csvs and tsvs and use ripgrep. I'm too lazy to come up with a real db solution at the moment.

My opinion relates to just data in general, but if you’re working with JSON and the person that created it wasn’t that smart it can be a pain to use for anything, CSV is usually where people have more chances to fuck up and everything still be smooth.

(March 24, 2022, 11:04 PM)somebody Wrote: Hello.

I am interested to hear your thoughts on which format you prefer downloading databases/leaks/data in.

I often find myself working with JSON when I run web scrapers, and when I write tools for transforming and processing data sets, I tend to use JSON too.

im a slut for csv id pay more just to have the data in csv format i love csv so much omg.

(March 25, 2022, 05:58 AM)xam Wrote: It depends on the data as some MongoDBs get weird. Usually I prefer CSV for quick parsing.

agree, it all depends on the type of DB and the content itself.

but for editing and subsequent import, the best solution is csv with the use of delimiters

CSV, for sure!
Makes analysis much easier.

It depends on the type of data and parser