Myrna van Lunteren wrote:

Well, I can see that smaller differences are tested (test lang/timestampArith.java) but these values were pulled out of Sun's (jdbc) compliance test suite, and I thought one shouldn't modify those values? Lance, you may know more about that detail...
 
Should timestampdiff be able to handle the range of the two timestamps in this particular query?
These tests would only get run by the test suite if it shows the function being supported by the backend.

I have not done the math to determine if the values are in range.  The dml is allowed to be modified once assuming the issue is a range issue based on what a given backend supports
 
Myrna
 
On 11/28/05, Lance J. Andersen <[EMAIL PROTECTED]> wrote:
Myrna,

Try having the timestamp values closer together and give it a go.

-lance


Myrna van Lunteren wrote:
Hi,
 
Is this a bug? It seems to me it is...
 
In ij:
ij> create table tab1(TMSTCOL1 TIMESTAMP, TMSTCOL2 TIMESTAMP);
0 rows inserted/updated/deleted
ij> INSERT INTO tab1 VALUES ({ts '1994-06-12 11:20:10'},{ts '1996-05-10 10:07:05'});
1 row inserted/updated/deleted
ij> SELECT {FN TIMESTAMPDIFF(SQL_TSI_FRAC_SECOND,TMSTCOL1,TMSTCOL2)} FROM tab1;
1
-----------
ERROR 22003: The resulting value is outside the range for the data type INTEGER.
 
Thx,
Myrna

Reply via email to