Timeline for Decorating an existing database table with information that no one else cares about
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Aug 1, 2012 at 22:53 | comment | added | NoChance | @Brian, you are quite correct. | |
| Aug 1, 2012 at 22:26 | history | migrated | from programmers.stackexchange.com (revisions) | ||
| Aug 1, 2012 at 16:38 | comment | added | Brian | As Wyatt says, the benefit of an additional table is that the existing database table won't break. As an aside, if it is primarily users who care about their own last accesses, Option 1 may be a bit faster if UserID_PK_FK is the first indexed column rather than the last. | |
| Aug 1, 2012 at 16:23 | comment | added | Doc Brown | I guess your solution is good for a different kind of "consumer" than the OP meant, but oversized for this case. | |
| Aug 1, 2012 at 15:19 | history | answered | NoChance | CC BY-SA 3.0 |