[PHOENIX-6764] Implement Binary and Hexadecimal literals

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.2.0
• Component/s: core

Environment

Phoenix now supports binary string literals as defined by the SQL standard: X'AF23' for hexadecimal literals, and B'0101011100100010' for binary literals.
Binary values in explain statements are now returned in the above format.
getString() for BINARY type results now use the same formatting as the VARBINARY type.

• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 09/Aug/22 08:49
• Updated: 14/Sep/22 07:44
• Resolved: 14/Sep/22 07:32

Description

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.

Issue Links

• blocks: PHOENIX-6720 CREATE TABLE can't recreate column encoded tables that had columns dropped
• links to: GitHub Pull Request #1490