From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | "rajasekhar5c1(at)gmail(dot)com" <rajasekhar5c1(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #8613: getting null when null is concatenated with string |
Date: | 2013-11-22 19:40:58 |
Message-ID: | 1385149258.65373.YahooMailNeo@web162903.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"rajasekhar5c1(at)gmail(dot)com" <rajasekhar5c1(at)gmail(dot)com> wrote:
> when i fire below query on one of our servers
>
> select null || 'query' ,'|'
>
> the result is null nothing is displayed
>
> when i fire the same query on another server which has same
> version of postgresql server
>
> i am getting result as
>
> query
This is not a bug.
For community PostgreSQL, NULL is the correct result. It is what
is required by the SQL standard, since concatenating a known value
with an unknown value yields an unknown result.
> postgres version on both servers are
>
> 1) EnterpriseDB 9.2.1.3 on i686-pc-linux-gnu, compiled by gcc (GCC) 4.1.2
> 20080704 (Red Hat 4.1.2-52), 32-bit 2) EnterpriseDB 9.2.1.3 on
> x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2 20080704 (Red Hat
> 4.1.2-52), 64-bit
However, you are not running community PostgreSQL, you are running
EDB PostgreSQL Plus Advanced Server (PPAS), which has an Oracle
compatibility mode which treats an empty string and NULL as
more-or-less the same thing. Your best bet for such an issue would
be to open a support ticket with EDB.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-11-22 19:53:45 | Re: BUG #8613: getting null when null is concatenated with string |
Previous Message | Stefan Kaltenbrunner | 2013-11-22 19:12:26 | Re: BUG #8612: Truncate did not release disk space |