[teiid-issues] [JBoss JIRA] Commented: (TEIID-1412) Teiid should take care of salesforce query limits by itself

[Wanja Pernath (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572602#comment-12572602 ] 

Wanja Pernath commented on TEIID-1412:
--------------------------------------

Well, especially if IN contains a list of PK numbers which are 18 chars in SFDC, it would make sense to further limit the IN criteria size:

700 times 18 chars = 12.600 chars plus 700 * 3 chars (each ID is set in apostrophes plus a comma) which sums up to approx. 14.700 chars. 

And this is just for the IN criteria list. You would then like to include the SELECT statement and all the other conditions. 

When I've played with old MetaMatrix, I set the IN criteria limit to something between 250 and 300. I think Oracle has (had?) an IN limit of 256 elements. - I don't think a typical handwritten query would ever exceed this limit. However, calculated statements (for dependent joins for example) could easily extend this limit.

Where can I configure this constant?


Thanks a lot + best,
  Wanja


> Teiid should take care of salesforce query limits by itself
> -----------------------------------------------------------
>
>                 Key: TEIID-1412
>                 URL: https://issues.jboss.org/browse/TEIID-1412
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Salesforce Connector
>    Affects Versions: 7.1.1, 7.2, 7.3
>         Environment: Teiid 7.1.1 on EAP 5.1 with CXF
>            Reporter: Wanja Pernath
>            Assignee: Steven Hawkins
>
> Salesforce has a query string limit of 10.000 chars. When Teiid is calculating and executing a query like this:
> SELECT Opportunity where AccountId in (a,b,c,d,e,f,g,h,i)
> It could extend the 10.000 chars limit of Salesforce. Right now teiid just stops with an Exception. 
> Expected behavior is to have teiid splitting up the condition into correct portions and to execute the above query n times to circumvent the limit:
> SELECT Opportunity where AccountId in (a, b, c);
> SELECT Opportunity where AccountId in (d, e, f);
> SELECT Opportunity where AccountId in (g, h, i);

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira