But even those two have different dialects, it's never 'just SQL'. Procedural languages as a whole vary wildly in what they can do - you won't be doing complex logic with custom types on MySQL/MariaDB anytime soon, whereas Oracle or PostgreSQL will suffice. There seems to be this odd division between procedural SQL and regular SQL statements, where what you can do differs based on context, which is inconsistent.

There are relatively few universal (cross language) DB migration solutions out there, for example dbmate, every framework seems to have its own approach.

How am i supposed to put logging in the queries, without mixing the logging code with the other triggers and tables? What about debugging long running processes? What about adding breakpoints that i can trigger when a particular view or table is accessed? What about doing this on the server while i have a local app instance connected to the DB, or maybe even another app server? Why can't i step through the query execution and see how the filtered record count changes with each 'step'?Īpart from that, my problems are largely with the tooling around databases. Next up, debugging in databases is just really bad.

Furthermore, you really can't group views into logical packages based on their intent, now can you? So, with views you end up with something that's very much like your cluttered list of tables, which gets really hard to get a good overview of when you have about 300 of them. Now, you might suggest that using views works for this intent, but what about most DBMSes out there having silly naming rules and restrictions? I don't want to work with v_mtz_wg_priv_prod_attr because someone thought that having just a few dozen characters makes sense as a restriction. * probably 500 lines long but often used snippet */ It would be nice if i could store parts of queries under packages, to be able to write dynamic SQL more easily, instead of having to use tools like myBatis for this purpose: (see the bit about SQL fragments) Then, working with SQL and CTEs feels like going back from a language where functions are first class citizens to one where no such thing exists, just in regards to querying data. This is annoying when you have 5-10 CTEs and you need to test something in the middle. If i want to test the second query, i need to take the first and second ones, copy them into a new worksheet and then rewrite the second one not to have the alias but instead be the main query. I've always found it hard to articulate the problems that i have with SQL and with the 'WITH' CTEs, but let me try anyways.įor starters, i can never actually tests parts of those queries without rewriting the query up to the part that i want to test, for example:

Study sql on mac