RE: SQL JOIN with LIKE -- MIDRANGE-L

Subject: RE: SQL JOIN with LIKE
From: "Dennis Lovelady" <iseries@xxxxxxxxxxxx>
Date: Thu, 15 Apr 2010 19:14:10 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

That's what I thought as well. But it only returns 11 rows which I know
isn't right, because I can query them individually using multiple like
statements and I'm seeing over 1000 rows when I do it that way.

Ummm...
SELECT ... FROM TABLE1 T1
JOIN TABLE2 T2 on T1.FIELD LIKE '%'|| Trim(T2.PARTFIELD) ||'%'

I presumed you had the file set with varying-length data. Bad assumption.
Does that fix it? If not, then take a look at a few of the rows that are
selected manually but not in this method. What is the property that makes
those records not selected?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Tom Seaver: "What time is it?"
Yogi Berra: "You mean now?"

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SQL JOIN with LIKE , Ron Adams

This mailing list archive is Copyright 1997-2025 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.