Skip to main content

Timeline for Why should a key be made explicit?

Current License: CC BY-SA 3.0

13 events
when toggle format what by license comment
May 23, 2017 at 11:33 history edited CommunityBot
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Apr 13, 2017 at 12:42 history edited CommunityBot
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
May 10, 2016 at 21:22 history edited Vérace CC BY-SA 3.0
added 103 characters in body
Aug 25, 2015 at 17:09 history edited Vérace CC BY-SA 3.0
added 5 characters in body
Aug 3, 2015 at 15:17 history edited Vérace CC BY-SA 3.0
Clarified - fixed a typo.
Jul 11, 2015 at 3:16 comment added jpmc26 While I would never, ever suggest that you put no constraints in the database (You should always have a primary key and foreign keys at a bare minimum), you could avoid #3 by having all apps consume from a shared service (service oriented architecture). (That's probably something you should consider for multiple consumers, anyway, as doing every last integrity check you need in the database can get nightmarish, too. Think triggers everywhere making checks across tables and rows all the time.)
Jul 10, 2015 at 14:36 history edited Vérace CC BY-SA 3.0
Small improvement in the English.
Jul 10, 2015 at 6:24 comment added Vérace Read a few books (Date, Garcia-Molina...) and come back to us if you have specific questions (questions that are overly broad are considered off-topic here). p.s. Welcome to the forum :-)
Jul 10, 2015 at 5:36 vote accept dsaxton
Jul 10, 2015 at 5:36 comment added dsaxton Thanks for your answer. I'll probably need to learn more to fully understand it. (I don't actually belong to a team, I'm just learning about databases out of curiosity.)
Jul 10, 2015 at 5:31 history edited Vérace CC BY-SA 3.0
added 4 characters in body
Jul 10, 2015 at 5:19 history edited Vérace CC BY-SA 3.0
added 380 characters in body
Jul 10, 2015 at 5:10 history answered Vérace CC BY-SA 3.0