Re: In a view, how do I cause fields with possible NULLs to be treated as a blank string in a replace operation?
От | Rick Genter |
---|---|
Тема | Re: In a view, how do I cause fields with possible NULLs to be treated as a blank string in a replace operation? |
Дата | |
Msg-id | BANLkTin7uCqZ3JdmCDx2GSm2R3gRLvynGw@mail.gmail.com обсуждение исходный текст |
Ответ на | In a view, how do I cause fields with possible NULLs to be treated as a blank string in a replace operation? ("Asfand Qazi (Sanger Institute)" <aq2.sanger@gmail.com>) |
Ответы |
Re: In a view, how do I cause fields with possible NULLs to
be treated as a blank string in a replace operation?
|
Список | pgsql-general |
Either use '' as some_type, or use COALESCE(some_type, '').
--
Rick Genter
rick.genter@gmail.com
On Mon, Jun 27, 2011 at 9:53 AM, Asfand Qazi (Sanger Institute) <aq2.sanger@gmail.com> wrote:
Hello,
So I have am playing with a view to test the feasibility of a
technique for storing some data.
It basically goes something like this:
CREATE VIEW formatted_table AS
SELECT name,
replace(some_template, '@', some_type) AS some_field
FROM some_table;
some_template is something like 'foo@bar' or 'foobar' (note the
missing template character).
some_type is a single letter like 'a' or 'b', or it can be NULL.
The above view works fine for rows where some_type is a letter, and
some_field ends up as 'fooabar' or whatever.
However, when some_type is NULL, some_field ends up as NULL as well.
I understand that this is expected behaviour, but how do I cause the
view to treat a some_type of NULL as an empty string, so that
some_field simply ends up as 'foobar'?
Hope that was clear.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
Rick Genter
rick.genter@gmail.com
В списке pgsql-general по дате отправления: