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: delete function name key from schema if no overload left after drop #89184

Conversation

chengxiong-ruan
Copy link
Contributor

Backport fixes: #89046
Previously we just remove an overload from the slice when dropping a function. This is problematic if there's zero overloads left after the drop because it pretends that there is some function with the name but actually nothing. So we need to delete the key if there is not overload for the name.

Release note: None
Release justification: GA blocker bug fix.

@chengxiong-ruan chengxiong-ruan requested a review from a team October 3, 2022 14:37
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@ajwerner ajwerner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @chengxiong-ruan)

Copy link
Collaborator

@mgartner mgartner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Thanks for fixing this. :lgtm:

Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status: :shipit: complete! 2 of 0 LGTMs obtained (waiting on @chengxiong-ruan)

Backport fixes: cockroachdb#89046
Previously we just remove an overload from the slice when dropping a
function. This is problematic if there's zero overloads left after the
drop because it pretends that there is some function with the name but
actually nothing. So we need to delete the key if there is not overload
for the name.

Release note: None
Release justification: GA blocker bug fix.
@chengxiong-ruan chengxiong-ruan force-pushed the udf-delete-fn-name-key-if-no-overload branch from 7a9e8b6 to 5ae9e2c Compare October 3, 2022 15:22
@chengxiong-ruan
Copy link
Contributor Author

TFTR!
bors r+

@craig
Copy link
Contributor

craig bot commented Oct 3, 2022

Build succeeded:

@craig craig bot merged commit 9794be4 into cockroachdb:master Oct 3, 2022
@blathers-crl
Copy link

blathers-crl bot commented Oct 3, 2022

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from 5ae9e2c to blathers/backport-release-22.2-89184: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 22.2.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

opt: v22.2.0-alpha.4: index out of range when resolving a function
4 participants