-
Notifications
You must be signed in to change notification settings - Fork 2
Bug: Migration Script doesn’t set TopicReference versions #70
Copy link
Copy link
Closed
Labels
Area: SQLRelates to the SQL Server database objects; do not use for the repository.Relates to the SQL Server database objects; do not use for the repository.Priority: 1Severity 2: MajorStatus 5: CompleteTask is considered complete, and ready for deployment.Task is considered complete, and ready for deployment.Type: BugBehavior that is inconsistent with documented or expected behavior.Behavior that is inconsistent with documented or expected behavior.
Milestone
Metadata
Metadata
Assignees
Labels
Area: SQLRelates to the SQL Server database objects; do not use for the repository.Relates to the SQL Server database objects; do not use for the repository.Priority: 1Severity 2: MajorStatus 5: CompleteTask is considered complete, and ready for deployment.Task is considered complete, and ready for deployment.Type: BugBehavior that is inconsistent with documented or expected behavior.Behavior that is inconsistent with documented or expected behavior.
The migration script should set the
Versionof the migrated topic references to that of the sourceAttributeValue. This was inadvertently overlooked during development since, originally, topic references couldn’t be versioned. As a result, rolling back to a version from before the 5.0.0 version results in topic references getting deleted.Should ideally apply a retroactive patch for migrated topics by joining them against
Attributeswith a match betweenAttributeValueandtarget_TopicID.Similarly, the default version for existing relationships should be set to the first version of the topic, since relationships can now be versioned as well. This likely defaulted to the date of the migration.