[teiid-issues] [JBoss JIRA] (TEIIDSB-213) We have strange behavior with aliases

Steven Hawkins (Jira) issues at jboss.org
Tue Jun 30 09:47:02 EDT 2020


    [ https://issues.redhat.com/browse/TEIIDSB-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182991#comment-14182991 ] 

Steven Hawkins commented on TEIIDSB-213:
----------------------------------------

> As a solution I think need to add property for Teiid "Generate full qualified names" or other similar solution. Why used full qualified names always?

Presumably it was done that way to prevent ambiguity in join scenarios.  Since there is no documentation to indicate that some scenarios will behave differently with qualification, there was no reason to believe it isn't generally valid.

An option to no qualify names would therefore probably imply not to pushdown any joins.

> Or may be you can add SQL option as MAKEDEP to do not generate full qualified names? It is better solution because we can have more granularity of requests.

There is a feature called source hints that are a user level hint that is pushed to the source which could be used to control some of this behavior.  

Another option is to only qualify in join scenarios.  A simple query like the one you have here should then work, but likely wouldn't when there is a parent/child join.

> So, at now Teiid do not compatible with this Salesforce behavior 

You mean we are not compatible with their qualification bug.  Yes that is correct.

> We have strange behavior with aliases
> -------------------------------------
>
>                 Key: TEIIDSB-213
>                 URL: https://issues.redhat.com/browse/TEIIDSB-213
>             Project: Teiid Spring Boot
>          Issue Type: Bug
>          Components: datasource
>            Reporter: Renat Eskenin
>            Priority: Major
>         Attachments: Снимок экрана от 2020-06-26 12-37-40.png, Снимок экрана от 2020-06-26 12-38-04.png
>
>
> We have two SOQL
> SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5
>   
>  SELECT a.ArticleNumber,a.Id,a.KnowledgeArticleId,a.Language FROM Regular_Articles__kav a WHERE a.Language = 'it' LIMIT 5 
> This SOQL requests get different responses from SF because in second request we have alias for table.
> It is mystics from SF (we made bug in sf)
> How we can call
> SELECT ArticleNumber,Id,KnowledgeArticleId,Language FROM Regular_Articles__kav WHERE Language = 'it' LIMIT 5
>   in Teiid without aliases?



--
This message was sent by Atlassian Jira
(v7.13.8#713008)



More information about the teiid-issues mailing list