-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Update sequences to be stored by ID when doing backup/restore #60942
Copy link
Copy link
Closed
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Description
Describe the problem
There now exists functionality for newly created sequences to be renamed, since we are now storing references to sequences via their IDs. Currently, if we backup sequences in earlier versions (before this renaming functionality) and then restore them in newer versions (that do support sequence renaming), these restored sequences still behave like old sequence. This means that they are still stored via their names, and they cannot be renamed.
Expected behavior
We want restored sequences to behave like sequences created in newer versions. That is, restored sequences should be stored by ID and have the ability to be renamed. This means we'll have to update the existing tests as well (see #60957)
Jira issue: CRDB-3097
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)