| I agree regarding SQL views - it's probably the most frequently used way of reusing SQL code. > And even across vastly different domains, even if not directly reusable, SQL queries are still highly transferable. That's the point, they are probably transferable in the "copy, paste and tweak" sense which would be highly frowned upon in other popular languages. > But which data/processing related tasks is SQL a very poor fit for? I specifically called SQL "a DSL for data processing", I probably should have written "there are many domains that SQL is a very poor fit for" to be more clear. >In my experience it's much more common to actually see the opposite - inefficient usage of ORMs, exporting datasets only to then perform pre/postprocessing, often requiring building programming "jigs" to circumvent bottlenecks, etc when it could've been done in a more streamlined manner in the DB/warehouse. Totally agree. Lukas Eder has some nice presentations about it. |
>Totally agree. Lukas Eder has some nice presentations about it.
Thanks - I googled him and instantly recognized the JOOQ blog, quality stuff.