While I agree that “SQL Enjoyer” seems like a weird category, I personally love SQL. I’ve been using it professionally for over 20 years, and I’ve yet to encounter a more elegant, efficient, and practical language for handling data in a relational database. Every attempt I’ve seen to replace it with something simpler has fallen far short.
Which database systems were you dealing with, that didn’t allow variables? My personal favorite is PostgreSQL, which does allow them on scripting languages, such as PLPGSQL.
See, I don’t have to worry about such details. I work in corporate software dev, which means that everything is an MSSQL database where most of the tables contain only an ID of a table-specific format and a JSON blob. Why use an ORM when you can badly reimplement NoSQL in a relational database instead?
While I agree that “SQL Enjoyer” seems like a weird category, I personally love SQL. I’ve been using it professionally for over 20 years, and I’ve yet to encounter a more elegant, efficient, and practical language for handling data in a relational database. Every attempt I’ve seen to replace it with something simpler has fallen far short.
Which database systems were you dealing with, that didn’t allow variables? My personal favorite is PostgreSQL, which does allow them on scripting languages, such as PLPGSQL.
See, I don’t have to worry about such details. I work in corporate software dev, which means that everything is an MSSQL database where most of the tables contain only an ID of a table-specific format and a JSON blob. Why use an ORM when you can badly reimplement NoSQL in a relational database instead?
hey hey, there there. don’t worry. most of the major NoSQL DBs implement just as horrible of travesties
Yep.
PostgreSQL is where its at, everybody else just hasn’t figured that out yet.