|
Hello Neil,
I would use the date data type. The advantages are:
system supported date functions (durations, extractions, comparisons,
leap-year, etc)
direct query support (Query/400, OPNQRYF, SQL, ODBC, and most third
party
tools)
less space used in the database
The disadvantages are:
not easy to process from RPG/400
no PRTF or DSPF date fields (no big deal anyway, just move)
slightly slower performance using date fields (converting to/from
internal
DB format)
Regards,
Simon Coulter.
//----------------------------------------------------------
// FlyByNight Software AS/400 Technical Specialists
// Phone: +61 3 9419 0175 Mobile: +61 3 0411 091 400
// Fax: +61 3 9419 0175 E-mail: shc@flybynight.com.au
//
// Windoze should not be open at Warp speed.
//--- forwarded letter -------------------------------------------------------
> X-Mailer: TFS Gateway /222000000/223021754/223005105/223110748/
> Date: Tue, 10 Mar 98 12:23:56 +0000
> From: neil.williams@pocruises.com
> To: MIDRANGE-L@midrange.com
> Reply-To: MIDRANGE-L@midrange.com
> Subject: Specifying Dates in DDS
>
>
> I have always believed that the best and most efficient way (from a
> retrieval and manipulation point of view) to store dates in a physical
> file is in the format
>
> A CC 2S 0
> A YY 2S 0
> A MM 2S 0
> A DD 2S 0
>
> I've been asked to consider using;
>
> A DAT 8D
>
> Now I'm an old stick in the mud with tunnel vision, so can anyone tell
> me the pros and cons of both methods so that I can make an informed
> decision on this ?
>
> Neil Holley-Williams
> Southampton, UK
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
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.