June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-46) Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-46?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins closed TEIID-46. ------------------------------ > Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names > ------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-46 > URL: https://jira.jboss.org/browse/TEIID-46 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Reporter: Michael Walker > Assignee: Steven Hawkins > Priority: Minor > Fix For: 7.0 > > > This problem occurs in our transformation editor, and also occurs with real-time queries (e.g. from QueryBuilder/SQLExplorer, or any client). > If you reference a non-qualified table name, e.g. "myTable", in a query, we'll attempt to resolve it if it is a unique name. > Strangely, we don't do the same thing for virtual procedures, even if they are unique. Instead, you must use the fully-qualified name. There should be no disparity. This is a usability defect. > This also happens to greatly extend the size of virtual procedure code, making it harder to read and debug. -- 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

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-693) Equality comparison of JoinPredicate returns true even when JoinPredicate criteria is different

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-693?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-693. ------------------------------- > Equality comparison of JoinPredicate returns true even when JoinPredicate criteria is different > ----------------------------------------------------------------------------------------------- > > Key: TEIID-693 > URL: https://jira.jboss.org/browse/TEIID-693 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Priority: Minor > Fix For: 6.2.0 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > When comparing the following command objects the commands evaluate as equal when performing c1.equals(c2) even though the criteria is different in the two commands: > c1 = SELECT bqt1.smalla.intkey, bqt1.smallb.intkey, bqt1.smalla.intnum, bqt1.smallb.intnum FROM bqt1.smalla LEFT OUTER JOIN bqt1.smallb ON bqt1.smalla.intkey = bqt1.smallb.intkey AND bqt1.smallb.intnum = 1 > c2 = SELECT bqt1.smalla.intkey, bqt1.smallb.intkey, bqt1.smalla.intnum, bqt1.smallb.intnum FROM bqt1.smalla LEFT OUTER JOIN bqt1.smallb ON bqt1.smalla.intkey = bqt1.smallb.intkey > This is due to the method com.metamatrix.query.sql.lang.JoinPredicate.equals(Object obj) referencing itself when getting the criteria from itself and the obj being passed in: > ... > List thisCrit = this.getJoinCriteria(); > ... > List otherCrit = this.getJoinCriteria(); > ... -- 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

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-788) Change internal handling of insert with query expression

by Steven Hawkins (JIRA)

Change internal handling of insert with query expression -------------------------------------------------------- Key: TEIID-788 URL: https://jira.jboss.org/jira/browse/TEIID-788 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 An insert with a query expression should be our dominant internal model. Select into should be rewritten as it instead of the other way around. -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-866) AdminShell is not able to handle SELECT * INTO #TEMP FROM foo; (statement does not return a result set)

by Paul Nittel (JIRA)

AdminShell is not able to handle SELECT * INTO #TEMP FROM foo; (statement does not return a result set) ------------------------------------------------------------------------------------------------------- Key: TEIID-866 URL: https://jira.jboss.org/jira/browse/TEIID-866 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 6.2.0 Environment: Fedora 10, 6.2 Stable (GA) Reporter: Paul Nittel Assignee: Steven Hawkins Here's the crux of the issue: select * into #temp from bqt1.smalla; // Error: // Uncaught Exception: TargetError : at Line: 165 : in file: URL: jar:file:/home/pnittel/teiid62/adminshell/lib/teiid-adminshell-6.2.0.jar!/scripts/jdbc.bsh : throw e ; Target exception: com.metamatrix.jdbc.MMSQLException: Statement does not return a result set. Steve H. put it this way: "The into clause turns the statement into an insert, which does not have a result set - it only returns an update count. It does seem like AdminShell should handle that case. It's probably doing some parsing of the command and expecting it to return a resultset..." This same statement works fine in SQL Explorer. -- 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

14 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-728) Pushing blank-padded literals to source may fail to return correct results

by Paul Nittel (JIRA)

Pushing blank-padded literals to source may fail to return correct results -------------------------------------------------------------------------- Key: TEIID-728 URL: https://jira.jboss.org/jira/browse/TEIID-728 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.2.0 Environment: fedora 10, JDK 1.6, Teiid from 7/16/2009 Reporter: Paul Nittel Assignee: Steven Hawkins While reviewing possible CTC errors, it was noticed that SPACE(n) was not returning the number of spaces specified. We did see that going directly to Oracle worked correctly. Steve H. believes Oracle is returning a CHAR type and Teiid is trimming the values as a result. (It would not have if the return type was VARCHAR, like SQL Server returns.) -- 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

14 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-873) Add support for quoted identifier aliases

by Steven Hawkins (JIRA)

Add support for quoted identifier aliases ----------------------------------------- Key: TEIID-873 URL: https://jira.jboss.org/jira/browse/TEIID-873 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor The sql spec allows for creating quoted identifier aliases (containing spaces, the period delimiter, etc.). We should support this style of alias for maximum portability. The issue with allowing this is that the internals of revolving and metadata do not account for the delimiter character in a table or column name. -- 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

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-850) Misspellings in Teiid Reference Guide

by Paul Nittel (JIRA)

Misspellings in Teiid Reference Guide ------------------------------------- Key: TEIID-850 URL: https://jira.jboss.org/jira/browse/TEIID-850 Project: Teiid Issue Type: Bug Environment: Ref Guide PDF, dated 6/11/2009 Reporter: Paul Nittel Assignee: Steven Hawkins Section 5.2.3's title reads, "Examle Virtual Procedures" Table 6.2 contains the word "PESSIMITIC" There are possibly more; I just happened to spot these. I'm sure Docbook XML editors have excellent spelling checkers ;-) -- 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

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-853) Dynamic command projection should be positional

by Steven Hawkins (JIRA)

Dynamic command projection should be positional ----------------------------------------------- Key: TEIID-853 URL: https://jira.jboss.org/jira/browse/TEIID-853 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3 Dynamic commands using the as clause should match with the dynamic command based upon position, rather than name. For example exec string 'select x, y ...' as a string, b string; should work since the right number of symbols are projected. -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-404) 1-way and 2-way SSL to MMx must support different keystore file names within a cluster

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-404?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-404. ------------------------------- > 1-way and 2-way SSL to MMx must support different keystore file names within a cluster > -------------------------------------------------------------------------------------- > > Key: TEIID-404 > URL: https://jira.jboss.org/browse/TEIID-404 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.1.0 > Reporter: Larry O'Leary > Fix For: 7.0 > > > Defect Tracker #24283: File naming conventions require a keystore file to be prefixed with the machine's host name. This creates a problem when deploying certificates for use with SSL to a MetaMatrix System as the keystore on each MetaMatrix Server has a different name. Currently, the MMConsole only allows you to set a key store file name that will be used system wide. > We will need the ability to define a key store file name on a per host and possibly a per VM basis. This could be accomplished in many different manners. > The recommended implementation would be to simply move the SSL Resource configuration to the process and host level. This would allow an administrator to continue to use the Console to configure SSL. > At the host level, the administrator could set the default key store file name to be used for all VM(s) deployed to that host. At the VM level, the administrator could set a key store file name value that will override the default host level key store file name property. > This should also be done for the client trust store property to support 2-way SSL. -- 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

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-26) Need to add logic to determine if a command is deterministic

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-26?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins closed TEIID-26. ------------------------------ > Need to add logic to determine if a command is deterministic > ------------------------------------------------------------ > > Key: TEIID-26 > URL: https://jira.jboss.org/browse/TEIID-26 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.0 > > > Defect Tracker #24669: A recent case removed the logic in dependentselectnode that did not reexecute a subquery if it did not have correlated references. This logic can be added back if we can check if the command is deterministic. -- 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

14 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010