StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2397256
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-07T17:59:06.250
FavoriteCount
0
LastActivityDate
2010-03-07T17:59:06.250
LastEditDate
2017-05-23T10:33:02.283
LastEditorUserId
-1
OwnerUserId
282612
ParentId
2397200
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
It's a good and deep question, which undoubtfully cannot be seriously answered without understanding the types of workloads you will be dealing, the actual queries to be performed (you should profile them!), the variety of information to be versioned, and so forth. But as for a general approach, I'd start with a simple solution which you can experiment with and benchmark. From that specific case study, develop a more robust case that you elaborate using lessons-learnt from your initial attempt. Here is one good example right here: <a href="https://stackoverflow.com/questions/762405/database-data-versioning">Database - Data Versioning</a> Other examples exist, and reading your question I believe you need not just the audit trail, but the actual information as well (to be able to return in time to a specific version). In response to your specific question, whether to use triggers, I would approach it differently: have your business logic in stored procedures for Transactional-update/delete etc', which you can later update and make more complex. Why? because it's in "one place" and nothing can get around it, and because triggers are more associated with tables and atomic actions (update, delete) rather than transactions!! For performance, I'd simply mark the active record as part of the update stored procedure (or high level language procedure for that matter), instead of querying for the most recent version.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POData Versioning Advice
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USEtamar Laron
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.