Timeline for Why is naming a table's Primary Key column "Id" considered bad practice?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 12, 2017 at 0:14 | comment | added | Doug | +1, Hate seeing tables with columns like Posts.postID, Posts.postName where simply using post.id and post.name is far prettier. | |
| Mar 20, 2013 at 22:17 | comment | added | kevin cline | @DevinDixon: if you create debug views, then just once you need to assign better names to the view columns. But if you redundantly include the table name in the column names, all clients have to repeat them all the time whether or not it is useful. | |
| Mar 20, 2013 at 20:41 | comment | added | Devin Dixon | I would agree except for the more tedious to read. I actually prefer reading more descriptive column names and spending less time figuring out what that column actually is for. | |
| Apr 17, 2012 at 18:16 | history | made wiki | Post Made Community Wiki by HLGEM | ||
| Oct 20, 2011 at 21:10 | comment | added | kevin cline | @HLGEM: One can always qualify the column name with the table name. | |
| Oct 20, 2011 at 17:15 | history | edited | kevin cline | CC BY-SA 3.0 | add Groovy/Grails to frameworks using "id" |
| Oct 18, 2011 at 20:20 | comment | added | HLGEM | ID is far more tedious to read | |
| Oct 18, 2011 at 1:30 | comment | added | ocodo | +1 for "and more tedious to read." - naming conventions shouldn't be thought of as a band-aid for sloppy code, they should be improving readability as a primary concern. | |
| Oct 17, 2011 at 21:31 | history | answered | kevin cline | CC BY-SA 3.0 |