Timeline for Social (Classmate like) database schema appreciation
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 2, 2016 at 16:06 | answer | added | Tersosauros | timeline score: 1 | |
| Jan 7, 2016 at 15:42 | comment | added | beeks | i would break out the users table into a Users table and UserProperties table, joined by the PK Users_ID. The Users table would store information about the user that we don't need to keep a historical record of, like: Users_ID User_Create_Time Last_Logon_Date Password_Hash Failed_Logon_Attempts User_DOB etc.. Then on the UserProperties table Users_ID Property_ID EffectiveStartDate Property_Type Property_Value Then you can join the User to the property to the date and the time, to find the state of a user's information at any point in time. | |
| Jan 7, 2016 at 13:43 | comment | added | cProg | Thanks Beeks for comments. About the ability to keep track of name changes (timestamps of the name changes, password lockout counts, last logon times) do I have to add those new fields into the Users table? | |
| Jan 6, 2016 at 20:13 | history | tweeted | twitter.com/StackDBAs/status/684830217735696385 | ||
| Jan 6, 2016 at 19:12 | history | edited | cProg | CC BY-SA 3.0 | added 17 characters in body |
| Jan 6, 2016 at 18:40 | history | edited | Hannah Vernon♦ | CC BY-SA 3.0 | improved formatting |
| Jan 6, 2016 at 17:36 | review | Close votes | |||
| Jan 6, 2016 at 17:46 | |||||
| Jan 6, 2016 at 17:25 | comment | added | beeks | Just personal preferences, but to me your schema lacks the ability to keep track of name changes due to marriage, etc, timestamps of the name changes, password lockout counts, last logon times, physical addresses for schools, display names in the Contacts table, video name, profile photo titles/descriptions, blah blah blah. | |
| Jan 6, 2016 at 17:07 | history | asked | cProg | CC BY-SA 3.0 |