× 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.


  1.  Home
  2. RPG400-L
  3. May 2012

Re: Embedded SQL with Coalesce

On 31 May 2012 07:48, Tom E Stieger wrote:
Selecting on a simple where clause similar to A.artxyr = 'xxxyyyy'
resulted in the same plan as selecting on A.artxyr = 'xxx' || 'yyyy'.
The interesting thing was the optimizer actually seemed created a new
plan for the new query even though the resulting plans were the same.
Both plans used an index probe over the index created for the
selection criteria I used.

FWiW that new plan may have been either a change to a parameterized query, or perhaps modified an originally parameterized query to have an explicit versus implied CAST for the expression.? That is, the selection may have been adjusted to effectively [pseudo-syntax] one of:

A.artxyr = ?

A.artxyr = cast( ? like column artxyr )

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.