Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Thanks Robbie, yeah I didn't make it too clear. There's one small note next to ONE of the "By" columns in my mock schema that mentions they will sometimes be int FK's, too - easy to miss, I should have put that in my column notes. The particular system I'm working with now is an AD-based Windows Client app, so it was a little trickier. I just ended up storing Windows login names, instead of a GUID or SID, but in general (at least on the web), I would have a User table and a UserID stored in those. Thanks for the advice.

Adam Plocher
– Adam Plocher

2018-04-20 09:58:11 +00:00
Commented Apr 20, 2018 at 9:58
Oh, and with regard to the "Modified": I think that's a good idea. I've done it in the past, not sure why I haven't made a habit of it. In fact, some of these tables have an ongoing changelog from a trigger that records all changes to an identical table with "History" appended to the name and 2 additional cols: ChangeType (char(1) = [i]ns,[u]pd,[d]el)/ChangeDate. If I was to pick 1 column, Modified would be more appropriate terminology anyway since it could cover ins, upd, and del. So yeah, I should go with all 3 or just 1 in those cases I guess. Having 2 (ins, del) doesn't make sense...

Adam Plocher
– Adam Plocher

2018-04-20 10:03:23 +00:00
Commented Apr 20, 2018 at 10:03
@AdamPlocher Ah, OK - login names should be unique and so are a key of sorts. Just saw the varchar and assumed it was a name of some sort.

Robbie Dee
– Robbie Dee

2018-04-20 10:34:59 +00:00
Commented Apr 20, 2018 at 10:34

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »