November 2009 - teiid-issues - Jboss List Archives

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-46?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-46. --------------------------------- Resolution: Done This was fixed for Teiid in the CompositeMetadataStore, which will work for user level queries. Similar logic would need to be added to the designer's TransformationMetadata to allow partial name resolving at design time. > Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names > ------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-46 > URL: https://jira.jboss.org/jira/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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-46?page=com.atlassian.jira.plugi... ] Steven Hawkins reassigned TEIID-46: ----------------------------------- Assignee: Steven Hawkins > Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names > ------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-46 > URL: https://jira.jboss.org/jira/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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-145) Parse double quoted literals as identifiers by default

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-145?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-145: -------------------------------------- Changed the name of the execution property allowDoubleQuotedVariable to ansiQuotedIdentifiers, with a default value of true. Setting to false will approximate the old parsing logic. ParseInfo objects also have their default value set to true, but look at the system boolean property teiid.ansi_quoted_identifiers to override the behavior. Someone wishing to have the old default MetaMatrix (which may be required for legacy vdbs) behavior would need to override both settings. > Parse double quoted literals as identifiers by default > ------------------------------------------------------ > > Key: TEIID-145 > URL: https://jira.jboss.org/jira/browse/TEIID-145 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > > The allowDoubleQuotedVariable property should default to true, rather than false. > Need to make a special note of this in release notes. An unknown number of unit tests will be affected. -- 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, 1 month

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-46?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-46: -------------------------------- Fix Version/s: 7.0 (was: 8.x) Affects Version/s: 7.0 (was: 8.x) > Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names > ------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-46 > URL: https://jira.jboss.org/jira/browse/TEIID-46 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Reporter: Michael Walker > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-99) Stored procedures should work in multisource connector binding scenarios

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-99?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-99: -------------------------------- Fix Version/s: 7.1 (was: 7.0) pushing to 7.1 > Stored procedures should work in multisource connector binding scenarios > ------------------------------------------------------------------------ > > Key: TEIID-99 > URL: https://jira.jboss.org/jira/browse/TEIID-99 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.1 > > > Defect Tracker #24614: Stored procedures should work in multisource connector binding scenarios by adding another input parameter named SOURCE_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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-89) Data roles should account for the ability to create temp tables

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-89?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-89: -------------------------------- Fix Version/s: 7.1 (was: 7.0) pushing to 7.1 > Data roles should account for the ability to create temp tables > --------------------------------------------------------------- > > Key: TEIID-89 > URL: https://jira.jboss.org/jira/browse/TEIID-89 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.1 > > > Defect Tracker #24698: Data roles should account for creating temp tables. Right now all temp table creation is allowed. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-192) Add the ability to switch the identity on connections

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-192?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-192: --------------------------------- Fix Version/s: 7.1 (was: 7.0) pushing to 7.1 > Add the ability to switch the identity on connections > ----------------------------------------------------- > > Key: TEIID-192 > URL: https://jira.jboss.org/jira/browse/TEIID-192 > Project: Teiid > Issue Type: Feature Request > Components: Common, JDBC Driver > Affects Versions: 8.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Based upon oracle and sql server abilities, we should offer methods to assert and newly authenticate an identity on an existing connection. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-251) Support SQL 2003 order by with expressions

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-251?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-251. ---------------------------------- Resolution: Done Finished the work to add support for order by expression by using the rewriter. At a later time it would be good to add full support through the planner/processor/connector layer. > Support SQL 2003 order by with expressions > ------------------------------------------ > > Key: TEIID-251 > URL: https://jira.jboss.org/jira/browse/TEIID-251 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.0 > > Attachments: sort_expression.patch > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Defect Tracker #25000: SQL 2003 allows the order by clause to contain expressions instead of just simple simple symbol names. Since we already support expressions in the group by clause (which is actually against the SQL spec), it would make since to support expressions in the order by as well. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-886) Request for more statistical functions in Teiid

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-886?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-886: ------------------------------- Summary: Request for more statistical functions in Teiid (was: Request for more statistical functions in MetaMatrix) Are there any references to offerings by other database vendors? > Request for more statistical functions in Teiid > ----------------------------------------------- > > Key: TEIID-886 > URL: https://jira.jboss.org/jira/browse/TEIID-886 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.2.0 > Reporter: Debbie Steigner > > Please provide a richer set of aggregate functions, specifically statistical functions like population standard deviation, sample standard deviation, population standard variance, 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-886) Request for more statistical functions in Teiid

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-886?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-886: ------------------------------- Component/s: Query Engine Affects Version/s: 6.2.0 > Request for more statistical functions in Teiid > ----------------------------------------------- > > Key: TEIID-886 > URL: https://jira.jboss.org/jira/browse/TEIID-886 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.2.0 > Reporter: Debbie Steigner > > Please provide a richer set of aggregate functions, specifically statistical functions like population standard deviation, sample standard deviation, population standard variance, 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2009