| ▲ | valzam 3 hours ago | |
The big problem is that raw SQL has pretty bad type inference and linting support in most editors. A query builder can still give you a lot of type safety benefits. | ||
| ▲ | rmunn 3 hours ago | parent | next [-] | |
Autocomplete is making me lazy. If I don't see what I'm about to type within two or three characters, I feel like the IDE isn't doing its job of helping me. So being able to type `db.Cust` and autocomplete Customers is really nice. I do know SQL, but yes, the language servers usually have a harder time connecting the SQL to my backend code, whatever language it's in, without quite a lot of config fiddling that pretty much obviates any time savings I would have gained from autocomplete. | ||
| ▲ | Arch-TK an hour ago | parent | prev | next [-] | |
A query builder is not an ORM. ORMs build queries for you, but a query builder does not need to be an ORM. | ||
| ▲ | dadie 3 hours ago | parent | prev | next [-] | |
I think the bigger problem is that SQL is in almost every language a second-class citizen. And even calling it second-class can be seen as a stretch. | ||
| ▲ | pjmlp 2 hours ago | parent | prev | next [-] | |
Which is why one is better off using IDEs, especially those from DB vendors. | ||
| ▲ | ai_slop_hater 3 hours ago | parent | prev | next [-] | |
The problem is that there is no "SQL" — it's different for every database. | ||
| ▲ | threethirtytwo 3 hours ago | parent | prev [-] | |
[dead] | ||