Timeline for Is it reasonable to mark all columns but one as primary key?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Jul 28, 2015 at 17:59 | answer | added | TommCatt | timeline score: 6 | |
| Jul 28, 2015 at 15:44 | vote | accept | rubik | ||
| Jul 28, 2015 at 14:44 | answer | added | Erwin Brandstetter | timeline score: 4 | |
| Jul 27, 2015 at 17:24 | history | tweeted | twitter.com/#!/StackDBAs/status/625718298869649408 | ||
| Jul 27, 2015 at 16:31 | history | edited | rubik | CC BY-SA 3.0 |
added 23 characters in body
|
| Jul 27, 2015 at 15:56 | history | edited | rubik | CC BY-SA 3.0 |
added 670 characters in body
|
| Jul 27, 2015 at 14:27 | history | edited | Erwin Brandstetter |
edited tags
|
|
| Jul 27, 2015 at 14:24 | comment | added | Erwin Brandstetter | Closely related question (with answer) on SO: Do I need a primary key for my table, which has a UNIQUE (composite 4-columns), one of which can be NULL?. If any of the columns can be NULL, urgently consider this: dba.stackexchange.com/q/9759/3684. | |
| Jul 27, 2015 at 13:58 | answer | added | Erwin Smout | timeline score: 4 | |
| Jul 27, 2015 at 13:39 | review | First posts | |||
| Jul 27, 2015 at 13:52 | |||||
| Jul 27, 2015 at 13:39 | history | asked | rubik | CC BY-SA 3.0 |