November 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-710) DB2 does not support pushdown of null keyword as a select expression

by Steven Hawkins (JIRA)

DB2 does not support pushdown of null keyword as a select expression -------------------------------------------------------------------- Key: TEIID-710 URL: https://jira.jboss.org/jira/browse/TEIID-710 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 For example SELECT SmallA.IntKey, NULL FROM SmallA will fail. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-360) SQLServer SQLTranslator issues

by Steven Hawkins (JIRA)

SQLServer SQLTranslator issues ------------------------------ Key: TEIID-360 URL: https://jira.jboss.org/jira/browse/TEIID-360 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 The time literal for Access/SQLServer is incorrect - should use 1970 not 1900 Limit for a set op needs to use a subquery Support for repeat should be aliased to replicate -- 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, 9 months

1
7
0 / 0

[JBoss JIRA] Created: (TEIID-455) Config edits should use optimistic locking

by Steven Hawkins (JIRA)

Config edits should use optimistic locking ------------------------------------------ Key: TEIID-455 URL: https://jira.jboss.org/jira/browse/TEIID-455 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.x Config edits are atomic, but do not enforce consistency - the last one always wins. Optimistic locking should be used to properly ensure consistency. Also versions should be restorable. Currently it's not expected that multiple admins will be making changes concurrently, so this is not a critical issue. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-888) OptimisticWrapTransactionTests tests are failing

by Van Halbert (JIRA)

OptimisticWrapTransactionTests tests are failing ------------------------------------------------ Key: TEIID-888 URL: https://jira.jboss.org/jira/browse/TEIID-888 Project: Teiid Issue Type: Bug Components: Integration Tests Affects Versions: 7.0 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Critical 2 Tests are failing: - testSingleSourceBatchCommand - com.metamatrix.jdbc.MMSQLException: Unexpectedly reached the end of the batched update counts. - testMultipleSourceVirtualProceduralSelect - MMSQLException: Group has an access pattern which has not been met: group(s) [vm.p1]; access pattern(s) [Access Pattern: Unsatisfied [] History (see attachment for full stacktrace) -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Assigned: (TEIID-856) CTC Query Results have special characters in some cases depending on the OS causing unexpected results

by Paul Nittel (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-856?page=com.atlassian.jira.plug... ] Paul Nittel reassigned TEIID-856: --------------------------------- Assignee: Van Halbert (was: Paul Nittel) Have fun! > CTC Query Results have special characters in some cases depending on the OS causing unexpected results > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-856 > URL: https://jira.jboss.org/jira/browse/TEIID-856 > Project: Teiid > Issue Type: Bug > Components: Integration Tests > Affects Versions: 7.0 > Reporter: Warren Gibson > Assignee: Van Halbert > > In some cases query error results are being returned to CTC with special characters depending on the OS. This results in unexpected results since CTC use the same set of expected results for all OS versions. Please strip off special characters from query results in CTC to accommodate differences between OS behavior. -- 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
0
0 / 0

[JBoss JIRA] Commented: (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 commented on TEIID-251: -------------------------------------- A side effect here was to remove the logic that allowed for a sort string literal to specify a positional ordering. We still allow integer constants. > 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] Assigned: (TEIID-217) LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result

by Michael Walker (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-217?page=com.atlassian.jira.plug... ] Michael Walker reassigned TEIID-217: ------------------------------------ Assignee: Michael Walker > LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-217 > URL: https://jira.jboss.org/jira/browse/TEIID-217 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: Michael Walker > Priority: Minor > Fix For: 7.0 > > > If an attribute appears more than once, we should have some way to return all values. Currently, we only return one value, with no rhyme, reason, or determinism as to which one gets returned. Implementing this is difficult when multiple attributes appear more than once, of course. But a simple example of where this problem rears it's head is in modeling LDAP groups. Groups typically have repeating attributes to represent each member, and it would be nice to query all members of a given group, but impossible to do so with the current logic. > A sophisticated solution would create a normalized view of a DN, breaking out multi-valued attributes into a separate table that could be joined by a primary key. A simple solution might allow attributes to be flagged as "multi-valued", in which case, they could be maintained in a single denormalized table that represents all values in the DN. > If we build an importer for LDAP, we should consider how to best handle this issue in the importer design. -- 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-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-219?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-219: --------------------------------- Fix Version/s: 7.1 (was: 7.0) > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://jira.jboss.org/jira/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 7.1 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- 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-171) Add SQLXML Function for Extract()

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-171?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-171: --------------------------------- Fix Version/s: 7.1 (was: 7.0) > Add SQLXML Function for Extract() > --------------------------------- > > Key: TEIID-171 > URL: https://jira.jboss.org/jira/browse/TEIID-171 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.1 > > > We had a posting on the dev site (http://devcentral.metamatrix.com/node/2089809383) asking how they can retrieve an entire xml node from an input doc in a web service transformation instead of just the node text. Our current xPath function xPathValue() always return the text. We need something more like SQLXML extract()/extractvalue() so we can return the xml OR the text. -- 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] Created: (TEIID-887) CLONE -Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names

by Steven Hawkins (JIRA)

CLONE -Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names -------------------------------------------------------------------------------------------------------------------------- Key: TEIID-887 URL: https://jira.jboss.org/jira/browse/TEIID-887 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
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2009