[
https://issues.jboss.org/browse/TEIID-5193?page=com.atlassian.jira.plugin...
]
Ramesh Reddy updated TEIID-5193:
--------------------------------
Description:
Running a query with a correlated subquery in a HAVING clause, such as
{code:sql}
SELECT INTKEY, STRINGKEY
FROM BQT1.SMALLA AS A
WHERE NOT (INTKEY IN (10))
GROUP BY INTKEY, STRINGKEY
HAVING INTKEY = (SELECT MIN(STRINGKEY) FROM BQT1.SMALLA AS B WHERE A.INTKEY = B.INTKEY)
{code}
fails on the datasource with
bq. com.osisoft.rdsa.RdsaException: [PIOLEDBENT] HAVING condition cannot be nonaggregate.
This seems to be an issue on the Osisoft PI datasource side, as running the query directly
against the datasource produces the same failure.
was:
Running a query with a correlated subquery in a HAVING clause, such as
{code:sql}
SELECT INTKEY, STRINGKEY FROM BQT1.SMALLA AS A WHERE NOT (INTKEY IN (10)) GROUP BY INTKEY,
STRINGKEY HAVING INTKEY = (SELECT MIN(STRINGKEY) FROM BQT1.SMALLA AS B WHERE A.INTKEY =
B.INTKEY)
{code}
fails on the datasource with
bq. com.osisoft.rdsa.RdsaException: [PIOLEDBENT] HAVING condition cannot be nonaggregate.
This seems to be an issue on the Osisoft PI datasource side, as running the query directly
against the datasource produces the same failure.
Osisoft translator - correlated subquery on HAVING clause fails
---------------------------------------------------------------
Key: TEIID-5193
URL:
https://issues.jboss.org/browse/TEIID-5193
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 8.12.x-6.4
Reporter: Andrej Šmigala
Assignee: Ramesh Reddy
Running a query with a correlated subquery in a HAVING clause, such as
{code:sql}
SELECT INTKEY, STRINGKEY
FROM BQT1.SMALLA AS A
WHERE NOT (INTKEY IN (10))
GROUP BY INTKEY, STRINGKEY
HAVING INTKEY = (SELECT MIN(STRINGKEY) FROM BQT1.SMALLA AS B WHERE A.INTKEY = B.INTKEY)
{code}
fails on the datasource with
bq. com.osisoft.rdsa.RdsaException: [PIOLEDBENT] HAVING condition cannot be
nonaggregate.
This seems to be an issue on the Osisoft PI datasource side, as running the query
directly against the datasource produces the same failure.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)