May 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-904) Error executing the Procedural releational query with out a where clause

by Ramesh Reddy (JIRA)

Error executing the Procedural releational query with out a where clause ------------------------------------------------------------------------ Key: TEIID-904 URL: https://jira.jboss.org/jira/browse/TEIID-904 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 7.0 I have virtual stored procedure called "p1" which has no input parameters. When I execute this procedure either via select * from p1; or exec p1(); in both cases it fails with error Group has an access pattern which has not been met: group(s) [vm.p1]; access pattern(s) [Access Pattern: Unsatisfied [] History [[]]] Procedures with no input parameters should not be tested for Access patterns. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-754) LOCATE() function isn't being translated correctly by Oracle Connector

by Larry O'Leary (JIRA)

LOCATE() function isn't being translated correctly by Oracle Connector ---------------------------------------------------------------------- Key: TEIID-754 URL: https://jira.jboss.org/jira/browse/TEIID-754 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0, 6.0.0, 6.2.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Fix For: 6.2.0 The rewritten/translated query for the MMx LOCATE() function to Oracle's instr() function does not appear to be correct. SELECT locate(INTNUM, '234567890', 1) FROM SMALLA WHERE INTKEY = 26 Is being rewritten for Oracle as: SELECT instr('234567890', to_char(SmallA.IntNum), 2) FROM SmallA WHERE SmallA.IntKey = 26 In this case Oracle will return 0 for instr() because Oracle starts at position 1. The query should be: SELECT instr('234567890', to_char(SmallA.IntNum), 1) FROM SmallA WHERE SmallA.IntKey = 26 Furthermore, if I pass a negative value to LOCATE() it appears we assume position 1. If the negative value is sent to Oracle, Oracle goes from the end of the string. We should prevent this (if not already). In 5.5.1 the rewritten query is even different and may ore may not be correct. I have not checked 5.5.3/5.5.4 and/or Westport/Teiid. Here are the test cases that should cover this issue: public void testRewriteLocate() throws Exception { String input = "SELECT locate(INTNUM, 'chimp', 1) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', to_char(SmallA.IntNum), 1) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate2() throws Exception { String input = "SELECT locate(STRINGNUM, 'chimp') FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', SmallA.StringNum) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate3() throws Exception { String input = "SELECT locate(INTNUM, '234567890', 1) FROM SMALLA WHERE INTKEY = 26"; //$NON-NLS-1$ String output = "SELECT instr('234567890', to_char(SmallA.IntNum), 1) FROM SmallA WHERE SmallA.IntKey = 26"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate4() throws Exception { String input = "SELECT locate('c', 'chimp', 1) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT 1 FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate5() throws Exception { String input = "SELECT locate(STRINGNUM, 'chimp', -5) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', SmallA.StringNum, 1) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-882) Look into using javax.xml.xpath in the XML-Relational connectors.

by John Doyle (JIRA)

Look into using javax.xml.xpath in the XML-Relational connectors. ----------------------------------------------------------------- Key: TEIID-882 URL: https://jira.jboss.org/jira/browse/TEIID-882 Project: Teiid Issue Type: Task Components: XML Connector Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Using the javax.xml.xpath implementation might give us a more complete XPath capability (functions, etc). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1007) Remove unnecessary inline views over group bys

by Steven Hawkins (JIRA)

Remove unnecessary inline views over group bys ---------------------------------------------- Key: TEIID-1007 URL: https://jira.jboss.org/jira/browse/TEIID-1007 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Our check for removing a view layer only checks for a grouping node, it should check to see if any of the projected columns are used in the group by. e.g. instead of select max(c1) from (select c1 from table) v1 -> select max(c1) from table -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1097) Add support for nested table references

by Steve Hawkins (JIRA)

Add support for nested table references --------------------------------------- Key: TEIID-1097 URL: https://jira.jboss.org/browse/TEIID-1097 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 Our current approach to procedural relational queries that relies upon criteria is difficult to use and causes numerous problems, such as TEIID-32 and unclear applicability of default values. It would be easier to just add support nested table references. e.g. select * from t, table(... t.x) t1 Where the join between the procedure or query contained in the table expression is implied. See http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/c... for more on the usage constraints. This functionality is also needed by the XMLTABLE function. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-807) Develop the new Teiid Console using JOPR for its core framework

by Van Halbert (JIRA)

Develop the new Teiid Console using JOPR for its core framework --------------------------------------------------------------- Key: TEIID-807 URL: https://jira.jboss.org/jira/browse/TEIID-807 Project: Teiid Issue Type: Feature Request Components: Console, Jopr Plugin Affects Versions: 6.3.0 Reporter: Van Halbert Assignee: Van Halbert Use the the JOPR framework to develop the new Teiid console for administrating and monitoring a Teiid resource. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-988) 3 argument locate function on postgres reports the wrong value

by Steven Hawkins (JIRA)

3 argument locate function on postgres reports the wrong value -------------------------------------------------------------- Key: TEIID-988 URL: https://jira.jboss.org/jira/browse/TEIID-988 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Any time the locate third argument is greater than 1 the postgres translation is returning the wrong position value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-890) AdminShell runs as if bsh.interactive=false was specified, even though interactive

by Paul Nittel (JIRA)

AdminShell runs as if bsh.interactive=false was specified, even though interactive ---------------------------------------------------------------------------------- Key: TEIID-890 URL: https://jira.jboss.org/jira/browse/TEIID-890 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 7.0 Environment: Fedora 10, JDK Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode), 7.0 M1 build Reporter: Paul Nittel Assignee: Steven Hawkins I installed and started Teiid with a query testing VDB deployed. When I entered "SELECT * FROM Smalla;", it went back to the interactive prompt without displaying any data. Executing "bsh.interactive=true;" before the SELECT corrected the problem (otherwise I had to "printResults();") In previous versions this has worked as intended. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1102) Create a replacement for the text translator

by Steve Hawkins (JIRA)

Create a replacement for the text translator -------------------------------------------- Key: TEIID-1102 URL: https://jira.jboss.org/browse/TEIID-1102 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors, Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.0 The current solution for the text connector requires the use of an external metadata file. This complicates the user experience with integrating text. An alternative approach would be to offer a built-in table function for text parsing: TEXTTABLE(expression COLUMNS column [, column]* [DELIMITER char] [(QUOTE|ESCAPE) char] [HEADER [integer]] [SKIP integer]) AS identifier column := identifier datatype [WIDTH integer] If width is specified for one column it must be specified for all columns. If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and HEADER should not be specified. expression - the text content to process, which should be convertable to CLOB. DELIMITER sets the field delimiter character to use. Defaults to ','. QUOTE sets the quote, or qualifier, character used to wrap field values. Defaults to '"'. ESCAPE sets the escape character to use if no quoting character is in use. This is used in situations where the delimiter or new line characters are escaped with a preceding character, e.g. \, HEADER specifies the text line number (counting every new line) on which the column names occur. All lines prior to the header will be skipped. If HEADER is specified, then the header line will be used to determine the TEXTTABLE column position by case-insensitive name matching. This is especially useful in situations where only a subset of the columns are needed. If the HEADER value is not specified, it defaults to 1. If HEADER is not specified, then columns are expected to match positionally with the text contents. SKIP specifies the number of text lines (counting every new line) to skip before parsing the contents. HEADER may still be specified with SKP. this would be implicitly a nested table, so it could be used to process multiple files: select x.* from t, texttable(t.clobcolumn COLUMNS first string, second date SKIP 1) x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-739) JDBC Connector updates

by Steven Hawkins (JIRA)

JDBC Connector updates ---------------------- Key: TEIID-739 URL: https://jira.jboss.org/jira/browse/TEIID-739 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 The PostgreSQL translator should assume the use of a 8.0 jdbc client (supports back to the 7.2 server) so that we can remove DatePartFunctionModifer/ModifiedDatePartFunctionModifer also support for the bit functions should be added. The SQL Server translator / capabilities should be updated to assume the use of a 2005, DataDirect, or later driver (all support back to sql server 2000) so that support for most of the time functions can be added. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2010