Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 4 of 4 total |
Incorrect INTERVAL SECOND result |
Thu, Apr 19 2007 1:36 PM | Permanent Link |
"Ole Willy Tuv" | Tim,
The result of the following interval expression looks incorrect to me: select cast((timestamp'2007-04-18 16:16:43'-timestamp'1899-12-30 00:00:00') second as bigint) from dummy EDB 1.02 b1 returns the value -908892693. Mimer SQL returns the value 3386074603, and so does my own calculation using the following algorithm: cast((cast(timestamp'2007-04-18 16:16:43' as double precision)-cast(timestamp'1899-12-30 00:00:00' as double precision))*86400 as bigint) Ole Willy Tuv |
Thu, Apr 19 2007 6:40 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ole,
<< The result of the following interval expression looks incorrect to me: >> It's the same as the milliseconds issue - there's an overflow issue when the number of milliseconds or seconds is greater than High(Integer). -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Apr 19 2007 6:45 PM | Permanent Link |
"Ole Willy Tuv" | << It's the same as the milliseconds issue - there's an overflow issue when
the number of milliseconds or seconds is greater than High(Integer). >> OK, so I assume that a fix will be included in the next build ? Ole Willy Tuv |
Mon, Apr 23 2007 4:22 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ole,
<< OK, so I assume that a fix will be included in the next build ? >> Yep, as always. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, April 27, 2024 at 08:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |