]
Steven Hawkins resolved TEIID-3662.
-----------------------------------
Resolution: Done
The root cause was that the tuplebrowser expected the value set to be sorted, but it was
only being sorted when an order by against the index was specified.
IN predicate against a materialized/temp table index without an order
by returns wrong results
----------------------------------------------------------------------------------------------
Key: TEIID-3662
URL:
https://issues.jboss.org/browse/TEIID-3662
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.7
Reporter: Tom Arnold
Assignee: Steven Hawkins
Priority: Blocker
Fix For: 8.12, 8.11.3
Seeing strange behavior when doing a simple select from {{SPATIAL_REF_SYS}}.
This works as expected:
{code}
select srid, proj4text from spatial_ref_sys where srid in (3875,4326);
srid | proj4text
------+----------------------------------------------------------------------------------------------------------------
3875 | +proj=tmerc +lat_0=0 +lon_0=21 +k=1 +x_0=21500000 +y_0=0 +ellps=GRS80
+towgs84=0,0,0,0,0,0,0 +units=m +no_defs
4326 | +proj=longlat +datum=WGS84 +no_defs
(2 rows)
{code}
Swapping the values in the IN causes only one row to be returned.
{code}
select srid, proj4text from spatial_ref_sys where srid in (4326,3875);
srid | proj4text
------+-------------------------------------
4326 | +proj=longlat +datum=WGS84 +no_defs
(1 row)
{code}