Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sql/schemachanger: support ALTER PRIMARY KEY when index references exist within views / functions #124131

Open
fqazi opened this issue May 14, 2024 · 0 comments
Labels
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)

Comments

@fqazi
Copy link
Collaborator

fqazi commented May 14, 2024

Previously, the declarative schema changer would hang with validation errors if we had references inside views / functions using the index selection syntax (i.e. @. This was because the declarative schema changer did not have any mechanism in place to fix these references. As a short term fix in #123017 we have blocked such schema changes. But longer term we can support them by "fixing" such references.

Jira issue: CRDB-38713

Epic CRDB-31281

@fqazi fqazi added 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) labels May 14, 2024
@blathers-crl blathers-crl bot added this to Triage in SQL Foundations May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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)
Projects
SQL Foundations
  
Triage
Development

No branches or pull requests

1 participant