Ensure ConsolidateVersions addresses Relationships

`Relationships` operate a bit different than `TopicReferences` (7e322c0) since it is _expected_ that there will be multiple values per `Source_TopicID` and `RelationshipKey`; instead, updates are tracked via the `IsDeleted` column. This addresses the `Relationships` portion of #75.

Author: JeremyCaney

OnTopic.Data.Sql.Database/Utilities/Stored Procedures/ConsolidateVersions.sql

@@ -93,6 +93,34 @@ FROM	ExtendedAttributes
 WHERE	Version		> @StartDate
   AND	Version		< @EndDate
 
+--------------------------------------------------------------------------------------------------------------------------------
+-- CREATE CONSOLIDATED RELATIONSHIPS RECORD
+--------------------------------------------------------------------------------------------------------------------------------
+;WITH	TopicRelationships
+AS (
+  SELECT	Version,
+	RowNumber		= ROW_NUMBER() OVER (
+	  PARTITION BY		Source_TopicID,
+			RelationshipKey,
+			Target_TopicID
+	  ORDER BY		Version		DESC
+	)
+  FROM	Relationships
+  WHERE	Version		> @StartDate
+    AND	Version		<= @EndDate
+)
+UPDATE	TopicRelationships
+SET	Version		= @EndDate
+WHERE	RowNumber		= 1
+
+--------------------------------------------------------------------------------------------------------------------------------
+-- DELETE CONSOLIDATED RELATIONSHIPS
+--------------------------------------------------------------------------------------------------------------------------------
+DELETE
+FROM	Relationships
+WHERE	Version		> @StartDate
+  AND	Version		< @EndDate
+
 --------------------------------------------------------------------------------------------------------------------------------
 -- CREATE CONSOLIDATED TOPIC REFERENCES RECORD
 --------------------------------------------------------------------------------------------------------------------------------