|
|
|
|
|
by rodelrod
2983 days ago
|
|
I'm with you but in my experience it's a lost fight. Most of the projects I come across these days follow the id convention. The advantages of using person_id are even more obvious in multiple joins, such as a star schema where you can using(person_id) all the things, reducing both the typing and the cognitive load. I suspect that if this convention was more pervasive, programmers would be a little bit less afraid of diving into SQL. Well, at least we're settling with some convention, so it's not all bad. EDIT: typo |
|