[JBoss JIRA] (TEIID-5366) SQL string is incorrect with aliased all in group
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5366:
-------------------------------------
Summary: SQL string is incorrect with aliased all in group
Key: TEIID-5366
URL: https://issues.jboss.org/browse/TEIID-5366
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.0, 10.3.2, 10.2.3
SQL such as:
select pm1g2.* from pm1.g1 as pm1g2
After parse/resolve will be shown as the sql string:
SELECT pm1.g1 AS pm1g2.* FROM pm1.g1 AS pm1g2
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIID-5365) Remove function model support entirely
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5365:
-------------------------------------
Summary: Remove function model support entirely
Key: TEIID-5365
URL: https://issues.jboss.org/browse/TEIID-5365
Project: Teiid
Issue Type: Task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.0
Function model support has been deprecated for some time and should be completely removed from the server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIID-5361) Column metadata with set queries only reflects projected branch
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5361?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5361.
-----------------------------------
Resolution: Done
Added logic around unions and literals - mostly for string and decimal types.
> Column metadata with set queries only reflects projected branch
> ---------------------------------------------------------------
>
> Key: TEIID-5361
> URL: https://issues.jboss.org/browse/TEIID-5361
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> The logic in the MetaDataProcessor only considers the projected branch when determining attributes beyond type, thus it may not accurately represent the expected results.
> We should also look at returning metadata that is more specific to literal values. For example:
> select 'a'
> would return the generic type metadata for 'a', rather than a more specific length.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIID-5360) DatabaseMetaData nullsAreSortedLow should not be true
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5360?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5360:
---------------------------------------
I'll try to drive this from the server as we've allowed the admin to configure the server side default for some time now.
> DatabaseMetaData nullsAreSortedLow should not be true
> -----------------------------------------------------
>
> Key: TEIID-5360
> URL: https://issues.jboss.org/browse/TEIID-5360
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Driver
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> Since there isn't a hard guarantee of null sorts (without an explicit null sort) we should not indicate nulls are low in the DatabaseMetaData. This will leave all of the null sort methods as false, which may be an issue for some clients so a flag should be added to control this behavior.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months