Timeline for Why is naming a table's Primary Key column "Id" considered bad practice?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2015 at 2:10 | comment | added | alpav | Actually SO practice is not perfect. I would use this naming: PostType -> PostType.Id; AcceptedAnswer -> Answer.Id; OwnerUser -> User.Id | |
| Feb 13, 2015 at 20:49 | comment | added | Cypher | What it does prove is that this practice in no way prohibits the scalability and usefulness of an application. | |
| Oct 20, 2012 at 14:39 | comment | added | Pieter B | Whether something is used at stack or not does not prove if it's good or bad practice. | |
| Apr 18, 2012 at 15:52 | comment | added | GBa | How exactly does this prove anything about best practices? | |
| Apr 18, 2012 at 0:11 | comment | added | Sjoerd | My guess at the FKs, based on the names: PostTypeId -> PostTypes.Id; AcceptedAnswerId -> Answers.Id; OwnerUserId -> Users.Id. Why should a practice that is that easy be considered 'bad'? | |
| Apr 17, 2012 at 18:16 | history | made wiki | Post Made Community Wiki by HLGEM | ||
| Apr 17, 2012 at 12:47 | history | answered | Cyril Gandon | CC BY-SA 3.0 |