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



On 2/9/11 1:39 PM, Mike Wills wrote:
<<SNIP>> I finding myself doing a bunch of sub selects like:

where
date >= (SELECT DATE(CONCAT('20', CONCAT(YY, CONCAT('-'
, CONCAT( MM, (CONCAT('-', DD)))))))
FROM LIB/FILE')

Yes, each portion of the date is in separate fields.

<<SNIP>>

Or is there a better way?


First thing I would change is to use CONCAT as an operator instead of a function because I would rather not count parentheses :-)

Encapsulate the expression in a VIEW, and if on a release that supports an expression in an INDEX then also build the access path for that identical derivation\expression [derived key].

CREATE VIEW LIB/FILE_DT (table-column-list, DT) AS
( SELECT
F.*
DATE('20' CONCAT YY CONCAT MM CONCAT CONCAT DD
CONCAT '000000') AS DT
FROM LIB/FILE AS F
)
;
CREATE INDEX LIB/FILE_DT_IX ON LIB/FILE
( DATE('20' CONCAT YY CONCAT MM CONCAT CONCAT DD
CONCAT '000000') AS DT ASC)
;
... where
date >= (select DT from LIB/FILE_DT)

FWiW: '20' can often be a bad assumption, just as '19' [was]; the expression may need to be more extensive for full\expected effect.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.