Timeline for Why should a key be made explicit?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2015 at 10:48 | answer | added | Thomas Franz | timeline score: 5 | |
| Jul 11, 2015 at 9:48 | comment | added | Thorbjørn Ravn Andersen | If the database knows that a given field is a key, a side effect is that it can help you locate the row containing the key much much faster than if it needs to look through all the rows in the tables. Indexes are a very important part of why databases are useful. | |
| Jul 11, 2015 at 1:31 | history | tweeted | twitter.com/#!/StackDBAs/status/619680449510678528 | ||
| Jul 10, 2015 at 9:37 | answer | added | boot4life | timeline score: 7 | |
| Jul 10, 2015 at 5:58 | answer | added | nvogel | timeline score: 9 | |
| Jul 10, 2015 at 5:46 | comment | added | Andriy M | They are not needed for your database to work but they are needed for your data to "work" i.e. be consistent, because that is exactly how you are telling your database server to keep the information consistent. | |
| Jul 10, 2015 at 5:36 | vote | accept | dsaxton | ||
| Jul 10, 2015 at 5:10 | answer | added | Vérace | timeline score: 31 | |
| Jul 10, 2015 at 4:31 | comment | added | dsaxton | Just why are they declared at all? It seems very helpful, but is it actually necessary to have a database that functions? | |
| Jul 10, 2015 at 4:28 | comment | added | Vérace | Do you mean that if you have a UNIQUE key, why bother having a PRIMARY one? | |
| Jul 10, 2015 at 4:27 | review | First posts | |||
| Jul 10, 2015 at 6:23 | |||||
| Jul 10, 2015 at 4:24 | history | asked | dsaxton | CC BY-SA 3.0 |