[
https://issues.jboss.org/browse/TEIIDDES-1576?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-1576:
------------------------------------------
This is not a supported usage of a column name in source. This would not be generally
valid as any usage in a join could cause the column references to be ambiguous and would
likely not be worked as an enhancement given the workarounds of introducing a view layer
to achieve the same effect (assuming that the functions are applicable to Teiid) or using
the native-query feature effectively specify a source inline view.
Unnecessary table aliasing causing in pushdown query
----------------------------------------------------
Key: TEIIDDES-1576
URL:
https://issues.jboss.org/browse/TEIIDDES-1576
Project: Teiid Designer
Issue Type: Bug
Components: Data Preview
Reporter: Tom Johnston
Create a Added a table manually to an existing physical model (generated from JDBC
import). put source specific syntax as name in source for a column.
When previewed I get an error because the g0 predicate was added to the column thus
resulting in an invalid query.
I proved the point by copy/paste the atomic query to the source directly (via Squirrel)
it failed with the same error then removed the predicate references (both on column and
table) and it succeeded.
The source is Sybase.
The Name in source entered for the column was:
convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature)
which resulted in the following push down
SELECT
g_0.convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature)
FROM "pinspr"."dbo"."cdr_rad_obs" g_0
which when executed directly against sybase fails..
if the g_0 is removed entirely the query succeeds in against Sybase using Squirrel.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira