sql/schemachanger: create sequence can return an internal error on a missing prefix #106302
Labels
branch-master
Failures and bugs on the master branch.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
C-test-failure
Broken test (automatically or manually discovered).
O-rsg
Random Syntax Generator
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
When CREATE SEQUENCE was added to the declarative schema changer, the call that we used to resolve
the prefix for the sequences was one did return a fatal assertion. Instead, our resolution function
should return appropriate errors for missing databases/schemas.
Example statement
Jira issue: CRDB-29496
The text was updated successfully, but these errors were encountered: