Skip to content

sql/schemachanger/scbuild: ensure proper version gating for mixed-version state #79840

@ajwerner

Description

@ajwerner

Is your feature request related to a problem? Please describe.

We ought to produce the same elements in the mixed version state as we do in the old version. That's how we'll ensure compatibility. We need to both do that and to validate that we do that.

Describe the solution you'd like

We need to find a way to ensure that the same statement and initial state result in the same exact state protobufs between the previous version and the current version. We could do this in a variety of ways, including writing "golden" protos on a per-release basis or finding a way to link old code directly.

Describe alternatives you've considered
There might be some way to do this as an integration test. I don't know that that would be better.

Jira issue: CRDB-15895

Metadata

Metadata

Assignees

Labels

C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)GA-blockerT-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)branch-release-22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions