docs: UPSTREAM adds the Materialize DEALLOCATE-quoting report - #22
Merged
Conversation
…filed as their bug-report discussion #38605) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Adds the 25th Reported row: MaterializeInc/materialize#38605 —
DEALLOCATE "Name"keeps the quotes in the lookup, so psqlodbc's protocol-prepared_PLAN0x…statements cannot be released (the server half of the psqlodbc#208 pair; promised in the psqlodbc#208 test-results comment). Filed as a discussion because Materialize takes bug reports via Discussions; the status script skips non-issue URLs by design, so the live tracker still counts 24 — extending it to GraphQL discussions is a logged follow-up.