phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1145) Ensure CHAR type meets SQL standard
Date Wed, 06 Aug 2014 22:33:11 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088386#comment-14088386
] 

James Taylor commented on PHOENIX-1145:
---------------------------------------

Thanks for the comment, [~cartershanklin]. Yes, our CHAR type handles all of these cases.

> Ensure CHAR type meets SQL standard
> -----------------------------------
>
>                 Key: PHOENIX-1145
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1145
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>
> Phoenix pads CHAR type values with space characters. This can lead to odd results if
a character smaller than a space is used. In addition, our comparison logic ignores trailing
spaces, but there may be issues with this approach. See this Postgres thread: http://postgresql.1045698.n5.nabble.com/String-comparison-and-the-SQL-standard-td5740721.html
> In addition, CHAR only supports single byte characters as we assume that each CHAR is
a one byte to calculate offsets.
> We should investigate making CHAR more conformant.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message