RE: 00:00:00 or 24:00:00

A test is easy enough to run - at least in SQL - and I got this interesting result

select case when timestamp('2007-11-28-24.00.00.000000') < timestamp
('2007-11-29-00.00.00.000000') then 'less than' else 'equal ' end
case from sysibm/sysdummy1

gave me 'less than' as the result. Same with this one

SELECT case when timestamp(current date,'24:00:00') <
timestamp(current date + 1 days, '00:00:00') then 'less than' else
'equal ' end case FROM sysibm/sysdummy1

Now how about a test in RPG?

At 07:11 AM 11/28/2007, you wrote:

All this back and forth through the many e-mails is quite hexing.

Based on the quote below from Bruce's e-mail, am I correct in assuming the
following:

Nov. 28, 2007 0000 <> Nov. 28, 2007 2400
Nov. 28, 2007 2400 = Nov. 29, 2007 0000

Tks,

Glenn Gundermann
ggundermann@xxxxxx
(647) 272-3295

> If memory serves me right, the use of 24:00:00, to refer to the end of the
> day, is to accomodate previous (and long standing) standards used by the
> military. As such ISO 8601 indicates:
>
> <quote>
> day, calendar
> time-interval starting at [0000] and ending at [2400] (which is equal to
> the beginning of the next calendar day);
> typically a calendar day has a duration of 24 h
> </quote>
>
> It is confusing to have two accepted ways to represent the same point in
> time and I do recall that this has always been a sore point with the
> chief database architect back in Rochester -- but a point that he (and
> us) have to live with...
>
> Bruce Vining

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.