[JBoss JIRA] (TEIID-4238) Remove need for quotes around cursor name declarations/fetches
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-4238?page=com.atlassian.jira.plugin... ]
Johnathon Lee reopened TEIID-4238:
----------------------------------
> Remove need for quotes around cursor name declarations/fetches
> --------------------------------------------------------------
>
> Key: TEIID-4238
> URL: https://issues.jboss.org/browse/TEIID-4238
> Project: Teiid
> Issue Type: Enhancement
> Components: ODBC
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
> Fix For: 9.1, 8.7.8.6_2
>
>
> Attempting to declare a cursor without quotes results in an error similar to[1]. The quotes should be optional except in special cases, as this seems to match later standards (SQL2003). Performing fetch operations against the cursor have the same issue, where if the cursorname is not quoted, parsing errors occur.
> [1] Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "[*]DECLARE[*] cursorname CURSOR" at line 1, column 1.
> Was expecting: "alter" | "begin" | "call" | "create" | "delete" | "drop" | "exec" | "execute" | "insert" | "merge" ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4392) Expand star support
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4392:
-------------------------------------
Summary: Expand star support
Key: TEIID-4392
URL: https://issues.jboss.org/browse/TEIID-4392
Project: Teiid
Issue Type: Sub-task
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.1
The * construct will currently produce a null pointer exception. It should be supported if possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4391) NONDETERMINISTIC functions incorrectly optimized out of ORDER BY
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4391?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4391.
-----------------------------------
Fix Version/s: 9.1
9.0.3
Resolution: Done
Corrected the evaluatable check for non-determinism.
> NONDETERMINISTIC functions incorrectly optimized out of ORDER BY
> ----------------------------------------------------------------
>
> Key: TEIID-4391
> URL: https://issues.jboss.org/browse/TEIID-4391
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.13.2
> Reporter: Dave Nicodemus
> Assignee: Steven Hawkins
> Fix For: 9.1, 9.0.3
>
>
> The default for functions is to be deterministic, so without an argument only a single value is assumed and these functions are optimized out of ORDER BY clauses.
> We should be able to change this behavior by marking a function and NON-DETERMINISTIC in the VDB definition like this :
> CREATE FOREIGN FUNCTION F() RETURNS FLOAT OPTIONS (NAMEINSOURCE '"app1".F', DETERMINISM 'NONDETERMINISTIC');
> But doing this fails to prevent the function call from being optimized out of the ORDER BY.
> Work arounds are to use the function in an expression that involves a table column or add a no-op parameter to the function and pass a table column.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-2578) add/remove schema elements
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2578:
-------------------------------------
The following small correction to creation of DATA WRAPPER, adding the TYPE to support override translator types.
{code}
CREATE FOREIGN ( DATA WRAPPER | TRANSLATOR ) <translator-name> [ TYPE <base-translator-type> ] OPTIONS (...)
{code}
> add/remove schema elements
> --------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4391) NONDETERMINISTIC functions incorrectly optimized out of ORDER BY
by Dave Nicodemus (JIRA)
Dave Nicodemus created TEIID-4391:
-------------------------------------
Summary: NONDETERMINISTIC functions incorrectly optimized out of ORDER BY
Key: TEIID-4391
URL: https://issues.jboss.org/browse/TEIID-4391
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.13.2
Reporter: Dave Nicodemus
Assignee: Steven Hawkins
The default for functions is to be deterministic, so without an argument only a single value is assumed and these functions are optimized out of ORDER BY clauses.
We should be able to change this behavior by marking a function and NON-DETERMINISTIC in the VDB definition like this :
CREATE FOREIGN FUNCTION F() RETURNS FLOAT OPTIONS (NAMEINSOURCE '"app1".F', DETERMINISM 'NONDETERMINISTIC');
But doing this fails to prevent the function call from being optimized out of the ORDER BY.
Work arounds are to use the function in an expression that involves a table column or add a no-op parameter to the function and pass a table column.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months