From: | Andrei Kovalevski <andyk(at)commandprompt(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: problems with SELECT query results |
Date: | 2007-05-29 17:34:46 |
Message-ID: | 465C6436.60007@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Joshua wrote:
> I checked the table and found that none of my fields in the SELECT
> statement contain NULLs.
>
> Any other suggestions?
Why are you using such constructions in your query: ',' || ',' || ',' ?
May be this set of commas makes you think that some of your fields are
empty? Do you have empty fields in following query?
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%'
P.S. If you really need so many commas - use them in a single block....
',,,'
> PFC wrote:
>>> 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.
>>
>>
>> --No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.5.446 / Virus Database: 269.8.1/822 - Release Date:
>> 5/28/2007 11:40 AM
>>
>>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2007-05-29 17:41:36 | Re: Best way to prevent overlapping dates |
Previous Message | Ed L. | 2007-05-29 17:19:55 | Re: query log corrupted-looking entries |