Re: Still more SQL date weirdness (Trying again) -- MIDRANGE-L

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

Subject: Re: Still more SQL date weirdness (Trying again)
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Tue, 31 May 2011 14:29:07 -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>

Gary Thompson wrote:

Reminds me of a problem I had with STRSQL:
maybe "Change Session Attributes"
set Date format to "*ISO" will
give you better/expected results?

That solves the "++++++++" problem, but the WHERE clause,

WHERE CDATE>= DATE('2011-01-01') AND CDATE < DATE('2011-03-01')

still gives the same error.

Curiouser and curiouser.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Still more SQL date weirdness (Trying again) , Gary Thompson

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.