|
First of all, "believe that the customer's requirement" is a scary thought. Have you suggested true date fields? I suppose you could always build views or logical files that convert the zoned dates into real dates. And just use these for all your applications. Others have spoken their wisdom regarding sorting. And it's sage advice. Think also of stuff like the following sql and how it may affect your decision. CREATE TABLE QTEMP/LANDESS (FAKEDATE NUMERIC (8 , 0) NOT NULL WITH DEFAULT, FAKETIMESTAMP NUMERIC (14 , 0) NOT NULL WITH DEFAULT) INSERT INTO QTEMP/LANDESS VALUES(20050505, 20050505120101) select CAST((SUBSTR(CHAR(FAKEDATE),1,4) CONCAT '-' CONCAT SUBSTR(CHAR(FAKEDATE),5,2) CONCAT '-' CONCAT SUBSTR(CHAR(FAKEDATE),7,2)) AS DATE), CAST(CHAR(FAKETIMESTAMP) AS TIMESTAMP) FROM QTEMP/LANDESS ....+....1....+....2....+....3....+....4. CAST function CAST function 2005-05-05 2005-05-05-12.01.01.000000 ******** End of data ******** I thought it was freaking amazing that SQL found it easier to convert the timestamp than it was to convert a date. This did NOT work: select CAST(CHAR(FAKEDATE) AS DATE), CAST(CHAR(FAKETIMESTAMP) AS TIMESTAMP) FROM QTEMP/LANDESS Time for another DCR??? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Steve Landess" <sjl_abc@xxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 05/09/2005 10:21 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <midrange-l@xxxxxxxxxxxx> cc Subject "Date" fields Date field question... There may be a few exceptions, but in JDE all date fields are generally defined as a 6-digit julian format - 105001, for example, indicates 1-January-2005. 099001 indicates 1-January-1999. (The '1' prefix indicates that the date is in the 21st century, a '0' prefix indicates 20th century). Let's say you're defining a date/timestamp field (14,0 Zoned) -or- a date field (8,0 Zoned) in a non-JDE data base (DB2). Is our industry, is there a standard for populating these types of field? I have an idea as to how they should be populated, but would like another's opinion. Please do not confuse my question with the "date" data type that is now available. I believe that the customer's requirement is to have this field defined as a numeric field... Regards, Steve -- 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.