In a sense SQL is the (typewriter) QWERTY of query languages. Inconvenient by design.
In a sense SQL is the (typewriter) QWERTY of query languages. Inconvenient by design.
join purchase using (customer_id)
They only get cumbersome when you have schemas without consistent key names, complex join conditions, insist on uppercasing reserved words, or do all sorts of formatting acrobatics.So I guess I agree with you. A well designed schema makes reading and writing SQL a pleasure
It's hard to fight for those when surrounded by ORM first people. "Why call it customer_id in the customer table, call it id". Because I like using using. "But we don't care we rarely do SQL queries, why optimize for the rare cases?".
Enjoy your N+1 ORM only problem then.
It makes code a lot more readable
(On the other hand, sql is often embedded in other languages where it might not get properly coloured so… maybe)
I've used this feature in Pascal and Basic and my feeling is that it improves readability a lot, as it better highlights structure than just coloring. OTOH, I've used it mostly on monochrome 1-bit-per-pixel systems where coloring wasn't available. I believe it could be a matter of taste.