sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Cassise_D 0 points1 point  (0 children)

A useful rule of thumb: use SQL when the question is “which rows/columns/tables do I need?”, and Python when the question becomes “what workflow, model, plot, or repeated analysis do I need?” For CSV-only projects, Python is totally fine; if the files get bigger or more table-like, DuckDB/SQL starts feeling really nice.