[JBoss JIRA] (TEIID-4407) Salesforce delete/update without a predicate does nothing
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4407:
-------------------------------------
Summary: Salesforce delete/update without a predicate does nothing
Key: TEIID-4407
URL: https://issues.jboss.org/browse/TEIID-4407
Project: Teiid
Issue Type: Bug
Components: Salesforce Connector
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 9.1, 8.13.7, 9.0.4
An update or a delete without a where clause will not do anything as the logic to fetch ids will only happen when there are predicates.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4187:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1369487|https://bugzilla.redhat.com/show_bug.cgi?id=1369487] from NEW to ASSIGNED
> Extend support for PI OLEDB Enterprise Queries in OSI PI Translator
> -------------------------------------------------------------------
>
> Key: TEIID-4187
> URL: https://issues.jboss.org/browse/TEIID-4187
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.13.3
> Reporter: Al S
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
> Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf
>
>
> Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter.
> Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries.
> 1) Import table valued functions as Teiid procedures
> 2) Allow the pushdown of nested table joins
> 3) Update the PI translator to use the CROSS APPLY syntax.
> 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this?
> Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4187:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1369487
Bugzilla Update: Perform
> Extend support for PI OLEDB Enterprise Queries in OSI PI Translator
> -------------------------------------------------------------------
>
> Key: TEIID-4187
> URL: https://issues.jboss.org/browse/TEIID-4187
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.13.3
> Reporter: Al S
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
> Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf
>
>
> Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter.
> Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries.
> 1) Import table valued functions as Teiid procedures
> 2) Allow the pushdown of nested table joins
> 3) Update the PI translator to use the CROSS APPLY syntax.
> 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this?
> Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months