|
Problem IT31702
|
Status: Closed |
-1204 WHEN DATE FIELD CONTAINS 12/31/9999 AND UPPER INDEX FILTERIS USED
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
A
select
tab1.c1, tab2.c2, tab2.c3 from tab1, tab2
where tab1.c1 = 1
and tab1.c1 = tab2.c1
and tab1.c2 = date(tab2.c2);
can result in
1204: Invalid year in date
when tab1.c3 contains '12/31/9999'
Queryplan is:
2) tab2: INDEX PATH
Filters: (tab1.c2 = DATE
(tab2.c2 ) )
(1) Index Name: tab2_idx1
Index Keys: c1 c2 (Serial, fragments: ALL)
Lower Index Filter: (tab2.c2 >= EXTEND (tab1.c2 ,year to
second) AND tab1.c1 = tab2.c1 )
Upper Index Filter: tab2.c2 < EXTEND (tab1.c3 ,year to
second) + interval( 1) day to day
NESTED LOOP JOIN |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC4. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 (when available) or *
* 14.10.xC4. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC4. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 (when available) or *
* 14.10.xC4. *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC15 and 14.10.xC4. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.01.2020
10.12.2020
10.12.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
