Re: LIKE changing data type -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: LIKE changing data type
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Thu, 31 Oct 2024 09:08:52 -0700
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

On 10/31/24 9:06 AM, Patrik Schindler wrote:

Hello Justin,

Am 31.10.2024 um 13:45 schrieb Justin Taylor <jtaylor.0ab@xxxxxxxxx>:

We've encountered a situation where a LIKE() is making a PACKED variable when the referenced variable is ZONED.

Uhm. What is the use case of using LIKE() for a numeric comparison? Shouldn't be this be done through "(not) less, equal or more" aka < = >?

I read this as a LIKE clause in a declaration, not a LIKE predicate in a comparison.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.