[
https://issues.apache.org/jira/browse/PHOENIX-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583380#comment-17583380
]
ASF GitHub Bot commented on PHOENIX-6764:
-----------------------------------------
stoty commented on PR #1490:
URL: https://github.com/apache/phoenix/pull/1490#issuecomment-1223580368
1. Forgot to add it to the commit, I've pushed it now.
2. Yes, PBinary should take care of that. This only affects the parser,
otherwise everything should behave as if you specified a query parameter and
set it with setObject(byte[]).
3. The standard BINMARY->NUMERIC coercion mechanism should apply. I will add
a few tests for that.
> 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)
