You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
37
37
- Treat legacy CLR table-valued function return-column collation clauses as compatible during comparison when SQL Server ignores them in the effective return shape.
38
38
- Treat legacy explicit `NULL` tokens on CLR table-valued function return columns as compatible during comparison and preserve them during compatibility reconciliation when the rest of the definition matches.
39
39
- Treat equivalent legacy `Assembly` scripts as compatible during comparison when they differ only by banner comments, wrapped or case-varied hex payload formatting, `PERMISSION_SET` spacing, or quoted versus bracketed `ADD FILE` names.
40
+
- Rewrite programmable-object declaration lines to the current metadata name when SQL Server stores stale module text after an object rename.
41
+
- Fix table-trigger scripting after the declaration rewrite change by resolving trigger schema without referencing a non-existent `sys.triggers.schema_id` column.
40
42
- Trailing semicolon differences on `INSERT` statement lines in data scripts are now suppressed during comparison normalization; scripts emitted with and without statement terminators compare as compatible (#47).
41
43
- Legacy `TableData` scripts now compare as compatible when they differ from canonical output only by `SET IDENTITY_INSERT` semicolons or top-level `N'...'` string literal prefixes, including inside multi-line `INSERT ... VALUES (...)` statements.
42
44
- Empty separator lines are now ignored during `status` and `diff`, and whitespace-only separator lines compare as compatible after normalization.
Copy file name to clipboardExpand all lines: specs/04-scripting.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,6 +110,7 @@ The following types are defined in this specification family and not fully imple
110
110
-`SET QUOTED_IDENTIFIER <ON|OFF>` + `GO`
111
111
-`SET ANSI_NULLS <ON|OFF>` + `GO`
112
112
- Programmable-object body MUST be followed by `GO`.
113
+
- Programmable-object declaration lines MUST reflect the current metadata schema/name even when the stored module text is stale after an object rename.
113
114
- Object-level permissions and extended properties MUST be emitted after object DDL body.
114
115
- Canonical programmable-object whitespace MUST be:
115
116
- no blank line between the final header `GO` and the first definition line,
0 commit comments