November 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2145) DDL options clause with namespace prefix is failing to parse correctly

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2145: ----------------------------------- Summary: DDL options clause with namespace prefix is failing to parse correctly Key: TEIID-2145 URL: https://issues.jboss.org/browse/TEIID-2145 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.1 Reporter: Ramesh Reddy Assignee: Steven Hawkins when there is namespace prefix in the options clause with DDL metadata it fails to parse colon (:) as the prefix separator. for example ddl below will fail {code} SET NAMESPACE 'http://teiid.org/rest' AS REST; CREATE VIRTUAL PROCEDURE g1Table() RETURNS TABLE (xml_out xml) OPTIONS (UPDATECOUNT 0, REST:METHOD 'GET', REST:URI 'g1') AS BEGIN SELECT XMLELEMENT(NAME "all", XMLAGG(XMLELEMENT(NAME "row", XMLFOREST(e1, e2)))) AS xml_out FROM Txns.G1; END {code} either Teiid needs to find another delimiter or escape it or parser it as string rather than in id() in the parser -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1374) Nested correlated reference issue with rewritten queries

by Steven Hawkins (JIRA)

Nested correlated reference issue with rewritten queries -------------------------------------------------------- Key: TEIID-1374 URL: https://jira.jboss.org/browse/TEIID-1374 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins In a query such as "select * from bqt1.smalla where exists (select intnum from bqt1.smalla x where smalla.intnum = x.intnum and exists (select intnum from bqt1.smalla where exists (select intnum from bqt1.smalla x where smalla.intnum = x.intnum)))" we will inappropriately report that the top exists subquery has 2 correlated references since we see the more deeply nested smalla.intnum also. This is generally not a issue, it can introduce errors in places where subqueries are rewritten, such as with subquery optimization or inherently updatable view queries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
3
0 / 0

[JBoss JIRA] (TEIID-2116) Serialized datatype issue

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2116: ------------------------------------- Summary: Serialized datatype issue Key: TEIID-2116 URL: https://issues.jboss.org/browse/TEIID-2116 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 Serialized metadata will contain references to datatype entries that will be duplicated upon deserialization with system'vdb type entries. Ideally there should be only 1 representation of each unique type. In general we have a representation issue with datatypes, which are either system or vdb scoped, when we serialize just a MetadataFactory that only represents a schema. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2088) teiid-8.1.0.Alpha2-jdbc-jdk15.jar - java.lang.NoClassDefFoundError: java/sql/RowIdLifetime

by Bob Akers (JIRA)

13 years, 4 months

5
16
0 / 0

[JBoss JIRA] (TEIID-2130) DataNotFoundException inconsistency when used with engine

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2130: ----------------------------------- Summary: DataNotFoundException inconsistency when used with engine Key: TEIID-2130 URL: https://issues.jboss.org/browse/TEIID-2130 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 8.1 When a DataNotException is thrown from translator, the engine should wait until commancContext.dataAvailable() call before it can send the "next" request to translator. However when the dataAvaialble() is called, in the async mode the Reset and Execute are being called instead of "next". See the attached test case for the behaviour. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
8
0 / 0

[JBoss JIRA] (TEIID-2117) Add support for blob/varbinary with xmltable

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2117: ------------------------------------- Summary: Add support for blob/varbinary with xmltable Key: TEIID-2117 URL: https://issues.jboss.org/browse/TEIID-2117 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 blob/varbinary cannot be used as a column type with xmltable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2136) All virtual entries on a physical model

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2136: ------------------------------------- Summary: All virtual entries on a physical model Key: TEIID-2136 URL: https://issues.jboss.org/browse/TEIID-2136 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 Physical schema should still allow virtual entires (views/procedures/functions). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] (TEIID-2036) Use array comparison for dependent join using multiple attributes.

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2036: ------------------------------------- Summary: Use array comparison for dependent join using multiple attributes. Key: TEIID-2036 URL: https://issues.jboss.org/browse/TEIID-2036 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.1 Many jdbc sources support array comparison which is more efficient that expressing comparisons using a cross space of in predicates. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-1366) Merge VDB action should provide way to persist the results

by Ramesh Reddy (JIRA)

Merge VDB action should provide way to persist the results ----------------------------------------------------------- Key: TEIID-1366 URL: https://jira.jboss.org/browse/TEIID-1366 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.2 Reporter: Ramesh Reddy Assignee: Steven Hawkins Currently "merge vdb" admin action is memory resident and does not persist between server restarts. Need to explore way to make this action persistent. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

6
15
0 / 0

[JBoss JIRA] (TEIID-2138) Use of the PG DSN for for ODBC metadata queries can result in improperly escaped SQL

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2138: ------------------------------------ Summary: Use of the PG DSN for for ODBC metadata queries can result in improperly escaped SQL Key: TEIID-2138 URL: https://issues.jboss.org/browse/TEIID-2138 Project: Teiid Issue Type: Bug Components: ODBC, Query Engine Affects Versions: 7.7 Reporter: Johnathon Lee Assignee: Steven Hawkins Various clients (Cognos, Excel, DBVisualizer) exhibit different results when querying metadata. For instance: Querying ModeShape on a fresh 5.3 deploy. select relname from pg_catalog.pg_class c, pg_catalog.pg_namespace n where relname like E'ddl\\_alterable' and n.oid = relnamespace 0 Records select relname from pg_catalog.pg_class c, pg_catalog.pg_namespace n where relname like E'ddl\_alterable' and n.oid = relnamespace 1 Record: ddl_alterable select relname from pg_catalog.pg_class c, pg_catalog.pg_namespace n where relname like E'ddl\_alterab__' and n.oid = relnamespace 1 Record: ddl_alterable Looking at [1] per [2]. It seems proper escaping of the E'literal' syntax is not always being performed. The Third example above shows that a wildcard is being escaped and happens to match to a literal value it expects. [1] PostgreSQL also accepts "escape" string constants, which are an extension to the SQL standard. An escape string constant is specified by writing the letter E (upper or lower case) just before the opening single quote, e.g. E'foo'. (When continuing an escape string constant across lines, write E only before the first opening quote.) Within an escape string, a backslash character (\) begins a C-like backslash escape sequence, in which the combination of backslash and following character(s) represents a special byte value. \b is a backspace, \f is a form feed, \n is a newline, \r is a carriage return, \t is a tab. Also supported are \digits, where digits represents an octal byte value, and \xhexdigits, where hexdigits represents a hexadecimal byte value. (It is your responsibility that the byte sequences you create are valid characters in the server character set encoding.) Any other character following a backslash is taken literally. Thus, to include a backslash character, write two backslashes (\\). Also, a single quote can be included in an escape string by writing \', in addition to the normal way of ''. [2] http://www.postgresql.org/docs/8.3/interactive/sql-syntax-lexical.html#SQ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
19
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2012