AWS AmazonRDS documentation change
Summary
Restructured schema ownership/permissions section and added limitations for CREATE/ALTER VIEW syntax
Security assessment
The changes document compatibility limitations (schema permissions differences and view syntax restrictions) but do not address security vulnerabilities or describe security features. No evidence of security fixes or vulnerabilities mentioned.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/babelfish-compatibility.tsql.limited-implementation.md b/AmazonRDS/latest/AuroraUserGuide/babelfish-compatibility.tsql.limited-implementation.md index 938525524..3f8ed37ea 100644 --- a//AmazonRDS/latest/AuroraUserGuide/babelfish-compatibility.tsql.limited-implementation.md +++ b//AmazonRDS/latest/AuroraUserGuide/babelfish-compatibility.tsql.limited-implementation.md @@ -37,4 +37 @@ These minor differences in ROWVERSION/TIMESTAMP datatypes shouldn't have an adve - - - -**Schema creation, ownership, and permissions** – Permissions to create and access objects in a schema owned by a non-DBO user (using `CREATE SCHEMA `schema name` AUTHORIZATION `user name``) differ for SQL Server and Babelfish non-DBO users, as shown in the following table: + * Schema creation, ownership, and permissions – Permissions to create and access objects in a schema owned by a non-DBO user (using `CREATE SCHEMA `schema name` AUTHORIZATION `user name``) differ for SQL Server and Babelfish non-DBO users, as shown in the following table: @@ -46,0 +44,9 @@ Access objects created by DBO in the schema without additional grants? | Yes | + * CREATE OR ALTER VIEW / ALTER VIEW syntax – The support for these syntax in Babelfish has the following limitations: + + * These statements cannot be used on views that have an INSTEAD-OF trigger attached. + + * These statements cannot be used on views that have another view based on this view. + + + +