× 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. MIDRANGE-L
  3. June 2011

Re: Still more SQL date weirdness

rob@xxxxxxxxx wrote:
Good ideas Chuck, although I suspect James will modify the condition handler to do something like
declare continue handler for SQLEXCEPTION return date('00010101000000')
since he didn't use null for that zero date. Then again, if he picked date('00010102000000')
it might make it easier to find dates that are invalid.

The problem is apparently *not* one of dates being invalid in the DISPLAYDAT UDF (and therefore in the view), or it would have been throwing exceptions without the WHERE clause. Rather, somehow, the DATE function, when called in the WHERE clause, appears to be expecting a 2-digit year, even though the session has been set to *ISO, and complaining when it doesn't get one.

Otherwise, it would still be failing when given 2-digit years in the WHERE clause.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.