Re: AW: Locate vs Like -- 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: AW: Locate vs Like
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Tue, 26 Jun 2012 09:59:07 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 26 Jun 2012 09:19, Vern Hamberg wrote:

I still don't see how Class.snapshotpath is an SQL column - looks
more like a qualified data structure subfield

Correlation identifiers used to identify a column follow that same naming convention. To me, the name Class.snapshotpath "looks like" a qualified column name when part of an SQL statement; e.g.:

select class.* , ...
from theTable class ...
where class.snapshotpath ...

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: AW: Locate vs Like , Vern Hamberg

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.