home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT04181 Status: Closed

WRONG RESULTS WHEN COMPARING TIME SERIES VALUES

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
Consider the following select: 
select "vts_v" as tablename, * from vts_v 
  where tmstamp <> tmstamp::datetime year to second; 
 
This tries to compare a time series to the truncated part, to 
try and find 
if there are data which differ only in the micro seconds part. 
 
In 12.10 this will display all rows, even those with all "0" in 
the microsecond part. 
 
 
If you do the same result using the extend funtion it will show 
the right results i.e. those with a different micro second part. 
 
select "vts_v" as tablename, * from vts_v 
  where extend(tmstamp::datetime year to fraction(5), year to 
fraction(5)) <> tmstamp::datetime year to second;
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* TS vti queries with cast on a column in the where clause     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IDS-12.10.xC5                                      * 
****************************************************************
Local Fix:
Solution
Problem Fixed In IDS-12.10.xC5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.09.2014
16.10.2015
16.10.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC5 FixList
12.10.xC5.W1 FixList