adding a concatenated field in an SQL query breaks LIKE

[Peter Haworth]

Another thought on this.  Checking for your string in a concatenated string
will yield false positives if some of the characters in your search string
occur at the end of one of the concatenated columns and the rest occur at
the start of the next concatenated column. You might be better off checking
each column individually.

Pete
lcSQL Software
On Jul 13, 2014 12:05 PM, "Dr. Hawkins" <dochawk at gmail.com> wrote:

> On Sun, Jul 13, 2014 at 10:00 AM, Peter Haworth <pete at lcsql.com> wrote:
>
> > Still confused though.  There is no "$" wildcard available for the LIKE
> > operator, only "%" and "_"
> >
>
>
> That came from typing rather than pasting that line :)  The code that works
> has a %
>
>
>
> > One other possibility.  It seems the LIKE operator has problems with
> > non-ASCII characters - any chance asset includes some, perhaps accented
> > characters?
> >
>
> That *shouldn't* be possible.  And if so, I need a filter to prevent that
> from happening . . .
>
> However, given that the match works when breaking of the asset column to an
> OR, I doubt that reason, as it should bite there, too.  (Hmm, or should
> it?  maybe not.)
>
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>