LIKE quandary -- MIDRANGE-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: LIKE quandary
From: Justin Taylor <jtaylor.0ab@xxxxxxxxx>
Date: Tue, 19 Oct 2021 07:56:22 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I have a JOIN on two tables, and I have no control over the data. I've now
ran into a situation where one of the tables contains wildcard characters
that are fouling up the JOIN.

Table1.column:
0110 EXFN 01 ABCD

Table2.column
0110 EXFN 01
____ EXFN 01

The JOIN clause:
T2.column concat '%' LIKE T1.column

This has always worked fine, but in this case it's matching both rows in
Table2.

Any suggestions on this?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: LIKE quandary , Kevin Bucknum
Re: LIKE quandary , Tim Fathers

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.