×
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.
On 15/12/2009, at 11:53 PM, Glenn Hopwood wrote:
If you use numeric fields for your dates I think mmddyy has a more
'natural' sort then ddmmyy.
Only true within a given year. As soon as your dates span multiple
years any so-called sort using MMDDYY is messed up (unless you WANT to
group the same months together). Of course, DDMMYY is effectively
unsortable anyway so I suppose there's a weird logic that MMDDYY is
somehow better than DDMMYY.
The only sensible numeric date formats for a database field is
YYYYMMDD, CYYMMDD if you're strapped for space), or a day number from
a given reference point (hopefully further back than 1900-01-01).
With the database using a Scaliger number to represent dates the
visual format no longer matters as much although I think database date
fields should be *ISO. Convert them for display or print purposes.
I never understood why MMDDYY became so popular in the US. That
sequence of month number, day number, and year only makes sense when
written in text form (e.g., November 11, 1918) or when spoken (e.g,
August Fourteenth, Nineteen Forty Five). Even so, to many of us in the
rest of the world that's still an odd format and the day of the month
of the year (e.g., 2nd September, 1945) is more natural.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.