[JBoss JIRA] (TEIID-3254) Add supporting capabilities
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3254:
-------------------------------------
Summary: Add supporting capabilities
Key: TEIID-3254
URL: https://issues.jboss.org/browse/TEIID-3254
Project: Teiid
Issue Type: Sub-task
Components: Connector API, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
With spreadsheet queries LIKE is not supported in UPDATE/DELETE and only simple values are supported in the update change set.
We should add capabilities to account for these restrictions.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (TEIID-3240) Tranlator archetype creation: -Dversion option sets the version of parent
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3240?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3240:
------------------------------------
No, I think something is not right. I'll be working on this to get it finished by mid January.
> Tranlator archetype creation: -Dversion option sets the version of parent
> -------------------------------------------------------------------------
>
> Key: TEIID-3240
> URL: https://issues.jboss.org/browse/TEIID-3240
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Reporter: Juraj Duráni
> Assignee: Van Halbert
>
> If new translator is created using command line, -Dversion option is set as version of parent project instead of version of actual translator.
> pom file:
> <parent>
> <groupId>org.jboss.teiid</groupId>
> <artifactId>connectors</artifactId>
> <version>0.0.1</version>
> </parent>
> ...
> <groupId>org.jboss.teiid.test.translator</groupId>
> <artifactId>test-translator</artifactId>
> <!--version>0.0.1</version-->
> <packaging>jar</packaging>
> ...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (TEIID-3240) Tranlator archetype creation: -Dversion option sets the version of parent
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3240?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3240:
---------------------------------------
Is this out of date then?
> Tranlator archetype creation: -Dversion option sets the version of parent
> -------------------------------------------------------------------------
>
> Key: TEIID-3240
> URL: https://issues.jboss.org/browse/TEIID-3240
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Reporter: Juraj Duráni
> Assignee: Van Halbert
>
> If new translator is created using command line, -Dversion option is set as version of parent project instead of version of actual translator.
> pom file:
> <parent>
> <groupId>org.jboss.teiid</groupId>
> <artifactId>connectors</artifactId>
> <version>0.0.1</version>
> </parent>
> ...
> <groupId>org.jboss.teiid.test.translator</groupId>
> <artifactId>test-translator</artifactId>
> <!--version>0.0.1</version-->
> <packaging>jar</packaging>
> ...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (TEIID-3253) Expand allowed order by expressions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3253?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3253:
----------------------------------
Description:
with a non-simple query we won't allow derived expressions in the order by such as:
select max\(x), y from t group by y order by case when y is null then 0 else y end
We treat this ordering as unrelated - however it is expressed in terms of expressions from the select clause. Mondrian will generate queries of this form, which requires a workaround of modifying the dialect to use ansi null ordering.
was:
with a non-simple query we won't allow derived expressions in the order by such as:
select max(x), y from t group by y order by case when y is null then 0 else y end
We treat this ordering as unrelated - however it is expressed in terms of expressions from the select clause. Mondrian will generate queries of this form, which requires a workaround of modifying the dialect to use ansi null ordering.
Component/s: Query Engine
> Expand allowed order by expressions
> -----------------------------------
>
> Key: TEIID-3253
> URL: https://issues.jboss.org/browse/TEIID-3253
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
>
> with a non-simple query we won't allow derived expressions in the order by such as:
> select max\(x), y from t group by y order by case when y is null then 0 else y end
> We treat this ordering as unrelated - however it is expressed in terms of expressions from the select clause. Mondrian will generate queries of this form, which requires a workaround of modifying the dialect to use ansi null ordering.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (TEIID-3253) Expand allowed order by expressions
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3253:
-------------------------------------
Summary: Expand allowed order by expressions
Key: TEIID-3253
URL: https://issues.jboss.org/browse/TEIID-3253
Project: Teiid
Issue Type: Enhancement
Reporter: Steven Hawkins
with a non-simple query we won't allow derived expressions in the order by such as:
select max(x), y from t group by y order by case when y is null then 0 else y end
We treat this ordering as unrelated - however it is expressed in terms of expressions from the select clause. Mondrian will generate queries of this form, which requires a workaround of modifying the dialect to use ansi null ordering.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (TEIID-1091) Add remaining SQL/XML functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1091?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-1091.
-----------------------------------
Resolution: Done
Added several functions - xmlexists, xmlcast, and xmltext. Both xmlexists and xmlcast were implemented using existing functionality from xmlquery and xmltable respectively. Also casting to/from array types was left off of xmlcast for now - ideally we could reimplement this the other way around where xmlcast is the primary logic and xmltable calls it.
> Add remaining SQL/XML functions
> -------------------------------
>
> Key: TEIID-1091
> URL: https://issues.jboss.org/browse/TEIID-1091
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 7.1
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> We should add the remaining functions, xmlparse, xmlserialize, xmlroot, etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (TEIID-3252) Add remaining SQL/XML functions
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3252:
-------------------------------------
Summary: Add remaining SQL/XML functions
Key: TEIID-3252
URL: https://issues.jboss.org/browse/TEIID-3252
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.10
We should add the remaining functions, xmlparse, xmlserialize, xmlroot, etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months