[
https://issues.apache.org/jira/browse/PHOENIX-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583389#comment-17583389
]
ASF GitHub Bot commented on PHOENIX-6764:
-----------------------------------------
stoty commented on PR #1490:
URL: https://github.com/apache/phoenix/pull/1490#issuecomment-1223604963
I've checked the SQL2011 standard
On page 188 it says
> 20) It is implementation-defined whether the declared type of a <binary
string literal> is a fixed-length binary
> string type, a variable-length binary string type, or a binary large
object string type.
So using the BINARY is OK.
Phoenix won't coerce binary types to numeric types, so you cannot treat a
binary string literal as a number.
> Implement Binary and Hexadecimal literals
> -----------------------------------------
>
> Key: PHOENIX-6764
> URL: https://issues.apache.org/jira/browse/PHOENIX-6764
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> Currently there is no sane way to specify arbitrary binary and varbinary
> values in the query string.
> They can be set as variables for preparedstatements, and if the length
> corresponds to an existing type, then some casting gymnastics can be used to
> work around the problem, but I have not found a way to write a query that
> upserts an arbitrary three byte value into a binary/varbinary.
> The SQL standard defines Binary and Hex literals in the form ofÂ
> B'01010101001...' and X'0102AAF5...'
> Implement this in the parser.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
