Timeline for Is it good practice to always have an autoincrement integer primary key?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 21, 2016 at 7:40 | comment | added | Drunken Code Monkey | From personal experience, I wholeheartedly agree with the second half of your answer. You will need globally unique keys much, much less often than you will need fast and compact indexes. If you do need one, create a GlobalEntities table with an autogenerated ID and a UUID column. Then add an ExGlobalEntityId foreign key to the Customers table for example. Or use a hash of some of the values. | |
| Aug 17, 2016 at 8:50 | history | edited | miroxlav | CC BY-SA 3.0 | added 84 characters in body |
| Aug 17, 2016 at 7:43 | history | edited | miroxlav | CC BY-SA 3.0 | added 208 characters in body |
| Aug 17, 2016 at 7:34 | history | edited | miroxlav | CC BY-SA 3.0 | added 22 characters in body |
| Aug 17, 2016 at 7:28 | history | answered | miroxlav | CC BY-SA 3.0 |