3 ms·
> customer_id 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 usi
by arkh 2y ago
> customer_id
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.
- hipadev23 2y agoYeah exactly. A very different way of thinking. While there are exceptions always (friend table composed of user_id pairs), I view my database/schema as a namespace. So customer_id refers to the same entity across all my tables.
- euroderf 2y agoThis one is on the ground floor of my Dept of Pet Peeves.