Re: Still more SQL date weirdness -- MIDRANGE-L

Subject: Re: Still more SQL date weirdness
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Wed, 01 Jun 2011 09:00:18 -0700
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Still more SQL date weirdness , Dan Kimmel

This mailing list archive is Copyright 1997-2025 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.