pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: José Soares <jose@sferacarta.com>
To: Glenn Waldron <gwaldron@wareonearth.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Trouble with null text fields
Date: Tue, 13 Apr 1999 18:07:53 +0200
Message-ID: <37136BD9.9739CA5@sferacarta.com> (raw)
References: <004401be85c1$e21175d0$0800a8c0@glenn.kivex.com>



Glenn Waldron ha scritto:

> Using Postgres 6.5 beta (snap 12 apr), on Linux i386.  I moved up from
> 6.4.2 when I couldn't get things working.
>
> I'm having difficulty dealing with null text/varchar fields.  I need
> to be able to interpret null values as the null string '' for the
> purposes on concatenation.
>
> 1) ----
> For example, the query:
>
>     SELECT (field_one || field_two) from t1;
>
> Will return the concatenation of the two fields.  If either of the fields
> is null, it is interpreted as the empty string '' and the correct answer
> is printed.  But:
>
>     SELECT * from t1 where ( field_one || field_two = 'something' )
>
> This does NOT work is either field_one or field_two is null.  Same result
> with the textcat() function.
>
> 2) ----
> Next I tried using "case", getting a parse error at or near "then":
>
>     SELECT ( case field_one when null then '' else field_one end ) from t1;
>

This is the syntax that PostgreSQL understands:

select  case when field_one is null then  t||'?' else t||v end from t1;


>
> This one gave me "ERROR: copyObject: don't know how to copy 704":
>
>     SELECT ( case field_one when 'string' then 'other' else 'third' end)
> from t1;
>

Seems that PostgreSQL doesn't recognize this syntax yet.

>
> 3) ---
> I tried writing a function that takes a "text" type and returns '' is the
> string
> is null.  Never could successfully do a null test on a function parameter.
>
> 4) ----
> I also tried writing my own concat function, and found that passing
> null fields into a user function doesn't seem to work either.  So I tried
> passing the whole thing in as a TUPLE, since you can determine whether a
> field is null with the GetAttributeByName() call.
>
> The creation:
>
>     CREATE FUNCTION mycat(text,text) returns text as '/usr/.../file.so'
> langauge 'sql';
>
> This worked great, even with null values:
>
>     SELECT mycat(field_one, field_two) from t1;
>
> This crashed the backend, with a "Memory exhauted in AllocSetAlloc()" error:
>
>     SELECT * from t1 where mycat(field_one, field_two) = 'something';
>
> So I tried making an index, and got:  "DefineIndex(): Attibute t1 not found"
>
>     CREATE INDEX t1_ix on t1 ( mycat(t1) text_ops );
>
> Any help is appreciated!! Sorry for the novel!!  -glenn

Try this one:

create function coalesce(text) returns text as
'declare
 nonullo ALIAS FOR $1;
begin
        IF nonullo ISNULL THEN
            RETURN ''\\\\N'';
        ELSE
            RETURN nonullo;
        END IF;
 end;
' language 'plpgsql';





view thread (6+ messages)  latest in thread

Message-ID: <37136BD9.9739CA5@sferacarta.com>
Permalink:  ../37136BD9.9739CA5@sferacarta.com/
Also on:    postgresql.org/message-id/37136BD9.9739CA5@sferacarta.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: jose@sferacarta.com, gwaldron@wareonearth.com
  Subject: Re: [SQL] Trouble with null text fields
  In-Reply-To: <37136BD9.9739CA5@sferacarta.com>
  References: <004401be85c1$e21175d0$0800a8c0@glenn.kivex.com> <37136BD9.9739CA5@sferacarta.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox