Add SQL as a category in breaking API change policy#22179
Open
alamb wants to merge 3 commits into
Open
Conversation
alamb
force-pushed
the
alamb/breaking_changes_mo
branch
from
2c389cb to
cb692d4
Compare
alamb
commented
May 14, 2026
| - Marking a function as deprecated (`#[deprecated]`) | ||
| - Adding a new function to a `trait` with a default implementation | ||
|
|
||
| ### What is the public SQL API and what is a breaking SQL change? |
Contributor
Author
There was a problem hiding this comment.
The core reason for this API is to add this section
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
As we have discovered, sometimes seemingly minor changes in SQL semantics have caused non trivial downstream pain, for example the recent changes to NULL semantics in
ANY/ALL. SeeWhat changes are included in this PR?
Add a note to the the API guide making it clear that changes to SQL semantics are also API changes too and deserve extra attention.
Are these changes tested?
By CI
Are there any user-facing changes?
Clearer API docs