[ https://issues.jboss.org/browse/TEIID-2177?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-2177 at 10/1/12 3:33 PM: -------------------------------------------------------------- SalesForce: Expanded the native query support using the extension metadata property "{http://www.teiid.org/ext/relational/2012}native-query" on the SalesForce Tables. When user uses this property, during the construction of the query, except for the projection columns all other parts of the query will be replaced with the native query before the query is submitted to the SF.com for Ex: if Account table had native query set to "From Account where ID = 'foo'", and the query submitted to translator is "Select Name, ID from Account" then the query submitted to SF will like "Select Name, ID From Account where ID = 'foo'" LDAP: Expanded the native query support using the extension metadata property "{http://www.teiid.org/ext/relational/2012}native-query" on the LDAP Tables. When user uses this property, during the construction of the query, except for the projection columns all other parts of the query will be replaced with the native query before the query is submitted to the LDAPContext For Ex: If Employee table has the above property with this value "context-name=corporate;filter=(objectClass=*);count-limit=5;timout=6;search-scope=ONELEVEL_SCOPE;attributes=uid,cn", the name in source property is ignored for building the context name, search scope and filter and above query used just as in native procedures TEIID-2176 and result query sent to the LDAP context. was (Author: rareddy): SalesForce: Expanded the native query support using the extension metadata property "{http://www.teiid.org/ext/relational/2012}native-query" on the SalesForce Tables. When user uses this property, during the construction of the query, except for the projection columns all other parts of the query will be replaced with the native query before the query is submitted to the SF.com for Ex: if Account table had native query set to "From Account where ID = 'foo'", and the query submitted to translator is "Select Name, ID from Account" then the query submitted to SF will like "Select Name, ID From Account where ID = 'foo'" LDAP: Expanded the native query support using the extension metadata property "{http://www.teiid.org/ext/relational/2012}native-query" on the LDAP Tables. When user uses this property, during the construction of the query, except for the projection columns all other parts of the query will be replaced with the native query before the query is submitted to the LDAPContext For Ex: If Employee table has the above property with this value "context-name=corporate;filter=(objectClass=*);count-limit=5;timout=6;search-scope=ONELEVEL_SCOPE;attributes=uid,cn", the name in source property is ignored for building the context name, search scope and filter and above query used just as in native procedures TEIID-2166 and result query sent to the LDAP context. -- 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

[ https://issues.jboss.org/browse/TEIID-2177?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2177: --------------------------------------- switched the native-query handling for sf over to procedures and not tables, since soql lacks inline view support. the native-query logic is tied into the direct execution usage of operation prefixes. also changed the delete operation to use the variable list as the delete targets to simplify the query string. The same conversion may be needed for ldap as well. -- 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