|
The DATE() function already exists -------------- Original message -------------- From: "Mohammad Tanveer" <mtanveer@xxxxxxxxxxxxxxxxx> > Interesting it seems like people who were born before 1940 have invalid DOB > :-) > > One solution might be to create a function like DATE(), meaning YOURDATE() > which can return you a valid date. > > Thanks > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard ECUYER > Sent: Thursday, January 05, 2006 9:02 AM > To: Midrange Systems Technical Discussion > Subject: Re: date data types, formatting in STRSQL > > You can use F13 and change the session attibutes to show date in *iso > format. > In a format with 2 digits for the year, the range is from 01/01/40 to > 31/12/39 other dates are invalids... > > ----- Original Message ----- > From: "rick baird" > To: "Midrange Systems Technical Discussion" > Sent: Thursday, January 05, 2006 4:38 PM > Subject: date data types, formatting in STRSQL > > > > Hey all, > > > > Is there any way to change the way date data types are formated when > > displayed in a STRSQL session? > > > > I tried: > > SELECT mydatefield from myfile > > and > > SELECT DATE(mydatefield) from myfile > > and > > SELECT CAST(mydatefield as date) from myfile > > > > all three show the date as mm/dd/yy. > > > > STRSQL DATFMT(*ISO) DATSEP('-') has no effect on the above. > > > > SET OPTION DATFMT=*ISO is not allowed outside of a REXX or other > > imbedded sql HLL. > > > > what am I missing here? the problem is I have dates that are lower > > than 1935, (or whatever the cutoff date is) and they're showing up as > > ++++++++ > > > > I get a data mapping error on those dates when I run it with debug on. > > > > thanks, > > > > Rick > > > > -- > > 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. > > > > > > -- > 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. > > > > -- > 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. >
As an Amazon Associate we earn from qualifying purchases.
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.