Skip to content

Bug: SQL: VersionHistoryIndex: Should account for all versioned tables #78

@JeremyCaney

Description

@JeremyCaney

Currently, the VersionHistoryIndex doesn't take into account versions that were introduced via Relationships or TopicReferences. Ideally, those should be factored in, due to the scenario where there isn't an update to the Attributes or ExtendedAttributes.

In practice, this should be rare, since the OnTopic Editor will, by default, write an indexed LastModified and LastModifiedBy attribute for every save. If the change is done programmatically, or the LastModified attributes are disabled, however, we should ideally make sure all versions are still accounted for, even if no attributes were modified.

Metadata

Metadata

Assignees

Labels

Area: SQLRelates to the SQL Server database objects; do not use for the repository.Priority: 3Severity 0: Nice to haveStatus 5: CompleteTask is considered complete, and ready for deployment.Type: BugBehavior that is inconsistent with documented or expected behavior.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions