×
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.
The date format within your udf is WRONG for ISO. ISO string date format is yyyy-mm-dd. What you have may be acceptable to CQE but it certainly is not to SQE. You may be experiencing an invocation of CQE in some of your queries and SQE in others. Change your UDF to include the hyphens and it should work in all circumstances.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Wednesday, June 01, 2011 11:00 AM
To: Midrange Systems Technical Discussion
Subject: Re: Still more SQL date weirdness
Mark Murphy/STAR BASE Consulting Inc. wrote:
Since that date function was built as a SQL stored procedure when you had your session defaults set to the 2 digit year format, it could be that the compiled routine is still expecting the two digit year format. Try recreating the stored procedure.
What stored procedure? The DISPLAYDAT UDF used in the VIEW explicitly sets the date format to *ISO, and it's compiled from a source member.
The DATE() call that appears (at least) to be throwing the exception is the one that's in the WHERE clause of an ad-hoc SELECT.
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
