Repository navigation
Treat trailing semicolon differences in INSERT statements as compatibility (a no-op) #44
Description
Description
When comparing scripting data outputs, differences consisting solely of missing/added trailing semicolons at the end of INSERT statements should be considered as compatible.
Current diff:
Object: data:SCHEMA.TABLE_NAME (TableData)
--- db
+++ folder
@@ -1,4 +1,4 @@
-INSERT INTO [SCHEMA].[TABLE_NAME] ([ID_COLUMN], [NAME_COLUMN]) VALUES (0, N'Group_A');
-INSERT INTO [SCHEMA].[TABLE_NAME] ([ID_COLUMN], [NAME_COLUMN]) VALUES (1, N'Group_B');
-INSERT INTO [SCHEMA].[TABLE_NAME] ([ID_COLUMN], [NAME_COLUMN]) VALUES (2, N'Group_C');
-INSERT INTO [SCHEMA].[TABLE_NAME] ([ID_COLUMN], [NAME_COLUMN]) VALUES (3, N'Group_D');
+INSERT INTO [SCHEMA].[TABLE_NAME] ([ID_COLUMN], [NAME_COLUMN]) VALUES (0, N'Group_A')
+INSERT INTO [SCHEMA].[TABLE_NAME] ([ID_COLUMN], [NAME_COLUMN]) VALUES (1, N'Group_B')
+INSERT INTO [SCHEMA].[TABLE_NAME] ([ID_COLUMN], [NAME_COLUMN]) VALUES (2, N'Group_C')
+INSERT INTO [SCHEMA].[TABLE_NAME] ([ID_COLUMN], [NAME_COLUMN]) VALUES (3, N'Group_D')
Acceptance Criteria
- Trailing semicolon differences for
INSERTSQL statements should result in compatible verdict. - Scripting logic should treat these cases as "compatible" or "no diff".
- Clearly document the expected behavior in code comments and any relevant project documentation.
Parent: #43
Activity
[-]Treat trailing semicolon differences in INSERT statements as incompatibility (not a no-op)[/-][+]Treat trailing semicolon differences in INSERT statements as compatibility (a no-op)[/+]