sql: add BIT(0) type
#132944
Open
sql: add BIT(0) type
#132944
+126
−27
Conversation
This file contains 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
The `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes cockroachdb#131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None
|
This change is |
|
I welcome bikeshedding on the name of this type. Another option I considered was |
mgartner
added
backport-23.2.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
sql: add
BIT(0)typeThe
BIT(0)type is now supported. It represents aBITtype withunspecified length. This is a divergence from Postgres which does not
allow this type and has no way to represent it in SQL. It is required in
order for it to be correctly serialized into SQL and evaluated during
distributed query execution.VARBIT cannot be used because it has a
different OID.
Fixes #131346
There is no release note because this bug is not present in any previous
releases and there is no need to document this new type.
Release note: None