Transactional schema change - support/error handling #97157
Labels
A-schema-changes
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Executing multiple ddl statements within a transaction results in the following:
Present day this can lead to friction in migration patterns and schema operations.
Request: better support for transactional schema changes or clearer errors/hints to eliminate friction
Jira issue: CRDB-24545
The text was updated successfully, but these errors were encountered: