Yeah, I saw that too. Frankly, that sucks.

Does anyone know if this just an iSeries DB2 thing, or does it also afflict the "other" DB2? I mean, ILE RPG and even SQL Server can calculate accurately durations between two date/time stamps.

--lg

On Jun 27, 2006, at 10:59 AM, rob@xxxxxxxxx wrote:

Study that timestampdiff bif carefully. A lot of assumptions are made. Which may, or may not, matter for your situation. Straight from the book:

The following assumptions may be used in estimating the difference:

there are 365 days in a year
there are 30 days in a month
there are 24 hours in a day
there are 60 minutes in an hour
there are 60 seconds in a minute
These assumptions are used when converting the information in the second argument, which is a timestamp duration, to the interval type specified in the first argument. The returned estimate may vary by a number of days.
For example, if the number of days (interval 16) is requested for a
difference in timestamps for '1997-03-01-00.00.00' and
'1997-02-01-00.00.00', the result is 30. This is because the difference between the timestamps is 1 month so the assumption of 30 days in a month
applies.


Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.