You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "SuperJDC (JIRA)" <ji...@apache.org> on 2016/01/20 03:25:40 UTC

[jira] [Closed] (HAWQ-356) varchar concat problem: one item is null || result would be NULL.

     [ https://issues.apache.org/jira/browse/HAWQ-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SuperJDC closed HAWQ-356.
-------------------------
    Resolution: Fixed

Though the result is not same to the oracle's result, same to mysql's result.

> varchar concat problem: one item is null || result would be NULL.
> -----------------------------------------------------------------
>
>                 Key: HAWQ-356
>                 URL: https://issues.apache.org/jira/browse/HAWQ-356
>             Project: Apache HAWQ
>          Issue Type: Bug
>            Reporter: SuperJDC
>            Assignee: Lei Chang
>
> Firstly, my hawq download from official website: https://network.pivotal.io/products/pivotal-hdb, a released stable version.
> SELECT 'a' || 'a' || 'a';
> result:
> aaa
> SELECT 'a' || NULL || 'a';
> result:
> NULL
> Anther steps;
> DROP TABLE IF EXISTS testconcat;
> CREATE TABLE testconcat(
> 	s1 VARCHAR(10),
> 	s2 VARCHAR(10),
> 	s3 VARCHAR(10)
> ) distributed randomly;
> INSERT INTO testconcat VALUES ('a', 'a', 'a'), ('a', NULL, 'a');
> SELECT s1 || s2 || s3 FROM testconcat;
> RESULT:
> aaa
> NULL
> It seems that using || joint varchars would be NULL (result) if one of the varchars is NULL. Is it operational character conflict?
> I followed the document steps and successfully integrated with the ambari. All of hawq configurations are the default.
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)