[JBoss JIRA] (TEIID-5457) Issues with sybase/ms sql pad pushdown
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5457?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5457:
----------------------------------
Description:
Sybase will return a non-null result then padding a null string.
Sybase and ms sql will trim from the string from the left when lpad is specified with a pad length shorter than the string. The expected behavior is to always trim from the right.
The length of the total string is also not computed correctly.
was:
Sybase will return a non-null result then padding a null string.
Sybase and ms sql will trim from the string from the left when lpad is specified with a pad length shorter than the string. The expected behavior is to always trim from the right.
> Issues with sybase/ms sql pad pushdown
> --------------------------------------
>
> Key: TEIID-5457
> URL: https://issues.jboss.org/browse/TEIID-5457
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.1
>
>
> Sybase will return a non-null result then padding a null string.
> Sybase and ms sql will trim from the string from the left when lpad is specified with a pad length shorter than the string. The expected behavior is to always trim from the right.
> The length of the total string is also not computed correctly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5343) Enable absolute URI on context definition of EntitySets when using ODATA
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5343?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-5343.
---------------------------------
Resolution: Done
See TEIID-5444
> Enable absolute URI on context definition of EntitySets when using ODATA
> ------------------------------------------------------------------------
>
> Key: TEIID-5343
> URL: https://issues.jboss.org/browse/TEIID-5343
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Affects Versions: 10.2.1
> Reporter: Rafael Sampaio
> Assignee: Ramesh Reddy
> Fix For: 11.1
>
>
> Hi all you TEIID guys.
> As reported on [OLINGO-1025|https://issues.apache.org/jira/browse/OLINGO-1025], integrating to MS OData consumers (ie. PowerBI/PowerQuery) gives the "should be an absolute Uri" error.
> The proposed solution in the JIRA is implementing a Processor for any given EntityType. Browsing through the code i see TEIID uses the ServiceHandler approach, instead of processor and it also has a Custom JSON Odata Serializer.
> I see that the Default JSON serializer, when serializing entity collections uses the ContextURL to generate the context metadata for the EntityCollection, but by default it does not contain the service root, since it comes from static DataRequest.buildEntitySetContextURL(olingo) method.
> Would be nice if we could choose this behavior through a init param in the odata deployment.
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5457) Issues with sybase/ms sql pad pushdown
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5457:
-------------------------------------
Summary: Issues with sybase/ms sql pad pushdown
Key: TEIID-5457
URL: https://issues.jboss.org/browse/TEIID-5457
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.1
Sybase will return a non-null result then padding a null string.
Sybase and ms sql will trim from the string from the left when lpad is specified with a pad length shorter than the string. The expected behavior is to always trim from the right.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (TEIID-5445) Atomic block is ignored when working with execute immediate command
by dalex dalex (JIRA)
[ https://issues.jboss.org/browse/TEIID-5445?page=com.atlassian.jira.plugin... ]
dalex dalex commented on TEIID-5445:
------------------------------------
[~shawkins] thx a lot for the quick fix, it worked.
> Atomic block is ignored when working with execute immediate command
> -------------------------------------------------------------------
>
> Key: TEIID-5445
> URL: https://issues.jboss.org/browse/TEIID-5445
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 10.2
> Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Fix For: 11.1, 10.3.4, 11.0.2
>
>
> When calling in atomic block a proc which is throwing an exception after updating some rows these changed rows won't be rolled back. That is running the following query:
> {code:sql}
> begin atomic
> call test_upd.upd();
> end ;;
> {code}
> all changes done in the test_upd.upd virtual procedure won't be rolled back in case of a thrown exception there. If I'm not mistaken such behavior was introduced in scope of TEIID-4504 issue (after introducing the Program.instructionsRequireTransaction method).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months