SQL Like vs. = sign -- 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: SQL Like vs. = sign
From: "Dan Bale" <dbale@xxxxxxxxxxxxx>
Date: Tue, 5 Oct 2004 10:45:53 -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>

I am setting up a dynamic SQL statement based on user input for data
selection.  They are able to select using wildcards, so I am using the LIKE
predicate to handle this.

My question is this:  When the user doesn't specify wildcards, and specifies
a "straight" value, is there any difference between using LIKE and an equal
sign?  I.e.:

CUSTNAME LIKE 'BALE, DAN'
CUSTNAME = 'BALE, DAN'

tia,
db

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: SQL Like vs. = sign , Erich W. Schasse
Re: SQL Like vs. = sign , Steve Landess

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.