RE: Better SQL performance than SUBSTRING -- 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: RE: Better SQL performance than SUBSTRING
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Fri, 4 May 2018 21:10:58 +0000
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Same results with " as KeySubstr".

-----Original Message-----
From: Dan [mailto:dan27649@xxxxxxxxx]
Sent: Friday, May 04, 2018 1:38 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Better SQL performance than SUBSTRING

Again, just a WAG, but I wonder if you need to explicitly name the indexed substring. So...
(SUBSTRING(MY_COLUMN,5,6)) as KeySubstr

No idea where "AUXILIARY' came from.

- Dan

As an Amazon Associate we earn from qualifying purchases.

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.