Re: Constraint comparing blanks.

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Bryce,

I was thinking Alan's issue might be related to '' vs. ' '....

So I tried it both ways.  Both cases work the same.

I'd say either Alan is missing a PTF or his Check constraint isn't
defined like he thinks it it.

The only way I could get <b>THOMAS<b><b><b>  to not work was to have a
constraint (fld1 not like ' %' )


Charles


On Fri, Apr 9, 2010 at 8:23 AM, Bryce Martin <BMartin@xxxxxxxxxxxx> wrote:
> Maybe I'm missing something, but wouldn't you just do NAME <> '';
>
> No space inside.  Then won't it look to see if the value you are comparing
> to is empty(all blanks)?  That is how I do it in my sql statements....
> then again, our text fields don't usually start with a blank so maybe I
> have potential bugs all over the place.
>
>
> Thanks
> Bryce Martin
> Programmer/Analyst I
> 570-546-4777
>
>
>
> Alan Campin <alan0307d@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 04/08/2010 07:38 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> Constraint comparing blanks.
>
>
>
>
>
>
> When you are declare DDL for an SQL defined table we use a lot of stuff
> like
> this
>
> NAME <> ' ';
>
> I would have thought that this would expand to be compare say 10 char name
> to 10 char blank but I saw today that is not true.
>
> If you have the following in a field name the test will fail because it
> only
> looks at the first character.
>
> <b>THOMAS<b><b><b> where <b> is a blank.
>
> What is the correct way to declare this test? In RPG you have a *ALL' '
> but
> not in SQL.
>
> You surely don't want to code
>
> NAME <> '          '
>
> I know there has to be a simple way to do it. Just can't think of it off
> the
> top of my head.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> --- This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us and destroy this message immediately. ---
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.