From: | Chuck Roberts <croberts(at)gilsongraphics(dot)com> |
---|---|
To: | PSql novice list <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Trouble with IN operator |
Date: | 2017-02-03 18:08:19 |
Message-ID: | CAByBP0rG0LGupes3xLqFDM-W9Z=sBuayDy_2shqe-Kj06f_Png@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
This is a vendor's database and we don't have control over it, nor do we
have direct access to the Postgresql table layouts. We are given a
spreadsheet to show us what the data types are.
As for the data, sometimes tbl.costcenter can be blank on some records.
Surely that wouldn't interfere with the IN operator?
Chuck
Thanks!
Chuck Roberts
Gilson Graphics | Composition Dept.
p:616-459-4539 x 1228
On Fri, Feb 3, 2017 at 12:37 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Fri, Feb 3, 2017 at 10:12 AM, Chuck Roberts <
> croberts(at)gilsongraphics(dot)com> wrote:
>
>>
>> AND (TRIM(tbl.costcenter) IN ('540'))
>>
>> Can anyone shed some light on this for me?
>>
>>
> It works...
>
> WITH tbl (id, costcenter) AS ( VALUES (1, '500'), (2, '550') )
> SELECT *
> FROM tbl
> WHERE (trim(tbl.costcenter) IN ('550'));
>
> So the problem resides in something you haven't show us - namely data.
>
> David J.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Campbell | 2017-02-03 18:14:47 | Re: Trouble with IN operator |
Previous Message | David G. Johnston | 2017-02-03 17:37:21 | Re: Trouble with IN operator |