Re: problems with SELECT query results

From: PFC <lists(at)peufeu(dot)com>
To: Joshua <joshua(at)joshuaneil(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: problems with SELECT query results
Date: 2007-05-29 16:25:50
Message-ID: op.ts3jxcpgcigqcu@apollo13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> SELECT 'PV.LINEITEM:' || partnum || ',' || round(onhand) || ',' ||
> round(qm5) || ',' || round(lsm4) || ',' || ',' || ',' || round(onorder)
> || ',' || ',' || ',' || binone || ',' || ',' || round(backorderqty) ||
> ',' || ',' || round(onhold) || ',' || ',' || ',' || ',' || ',' || ',' ||
> ',' || round(qtyperjob) || ',' || round(ordermax) AS gmrim FROM slparts
> WHERE vendor LIKE 'CH%'

You could select columns and build the string in your application ?

> The query does work and I am getting results from the database. There
> are values for all 'partnum' in the database, however, the query results
> include blank fields here and there in between the returned records. Why
> am I receiving blank fields for 'gmrim'???? This absolutely defies logic

Because one of your fields is probably NULL, and NULL || anything stays
NULL.

You have probably been misled to believe they are "blanks" because they
don't display as "NULL" but as "".
I set psql to display NULL as NULL.

If these columns can, must, or should not contain NULLs depends on your
application... it's for you to chose.
Use COALESCE, add NOT NULL constraints, grab the columns and build the
string in your application, you chose.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2007-05-29 16:36:01 Re: problems with SELECT query results
Previous Message Greg Sabino Mullane 2007-05-29 16:15:42 Re: Postgres / Jaro Winkler fuzzy string matching