April 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-177) Provide JDBC 3.0 JRE 1.5 backwards compatibility

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-177?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-177: ------------------------------------ I have added some language processing identifiers in the code like //## JDBC4.0-begin ## import java.sql.SQLXML; //## JDBC4.0-end ## /*## JDBC3.0-JDK1.5-begin ## import com.metamatrix.core.jdbc.SQLXML; ## JDBC3.0-JDK1.5-end ##*/ which by use of additional ant tasks during the build can turn ON or OFF certain portions of the code, that suits for the required 1.5 or 1.6 compilation of the code. The following projects have these processors teiid-common-core teiid-client teiid-client-jdbc A new project called teiid-client-jdbc30 has been added for purposes of building the JDK1.5 supported client jar file. This project copies the all the required java files from above projects and runs the language processors and builds 1.5 compatible code and builds the required jar file. I am not planning on putting any build related automation work, as they may be very time consuming right now, we will build it manually at release time and include in any kits. Testing is still pending. > Provide JDBC 3.0 JRE 1.5 backwards compatibility > ------------------------------------------------ > > Key: TEIID-177 > URL: https://jira.jboss.org/jira/browse/TEIID-177 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.x > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 6.1.0 > > > The jdbc driver needs to support jdk 1.5 on the client. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-524) Fix command logging regression - transaction id not logged by dqpcore

by Steven Hawkins (JIRA)

Fix command logging regression - transaction id not logged by dqpcore --------------------------------------------------------------------- Key: TEIID-524 URL: https://jira.jboss.org/jira/browse/TEIID-524 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 The txn id was not being sent to the tracking service. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Work started: (TEIID-203) Make connector capabilites more granular.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-203?page=com.atlassian.jira.plug... ] Work on TEIID-203 started by Steven Hawkins. > Make connector capabilites more granular. > ----------------------------------------- > > Key: TEIID-203 > URL: https://jira.jboss.org/jira/browse/TEIID-203 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Some connector capabilites are only available in combination with others. For example, if you wish to support the SupportsAggregatesCount capability, you have to also support the SupportsAggregates capability(GROUP BY and HAVING). This requirement creates additional requirements for a connector where the source syustem cabilities do not correspond with the relationships we have defined between capabilites. > For instance, the SQL supported by salesforce can include the count(*) function, but it does not support GROUP BY or HAVING. Because we require c connector to support SupportsAggregates befrore it can support count(*), the connector is required to implement those functions if it wishes to pus down count(*). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-124) insert with query should be supported at the connector level

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-124?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIID-124: ------------------------------------ Assignee: Steven Hawkins > insert with query should be supported at the connector level > ------------------------------------------------------------ > > Key: TEIID-124 > URL: https://jira.jboss.org/jira/browse/TEIID-124 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #25005: Insert into with a query is now supported at the query level and is the ANSI standard way of representing select into. Insert with a query should become the dominant concept rather than select into, and it should be supported through the connector layer so that same source operations do not have the overhead of a select into. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-523) hasWsdl attribute Not Set in VDB

by Ted Jones (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-523?page=com.atlassian.jira.plug... ] Ted Jones resolved TEIID-523. ----------------------------- Resolution: Done Added code to set the wsdlAvailable flag in VDBArchive. This was a regression from the refactoring of the VDBReader. > hasWsdl attribute Not Set in VDB > -------------------------------- > > Key: TEIID-523 > URL: https://jira.jboss.org/jira/browse/TEIID-523 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.1.0 > > > The hasWsdl attribute of a VDB should be set to true for VDBs that contain a MetaMatrixDataServices.wsdl file. Currently this value is false for Web Service VDBs. This attribute is used for the WSDL auto-discovery process. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-235) ENHANCEMENT: function resolving should also consider return type

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-235?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-235: --------------------------------- Fix Version/s: 6.1.0 (was: 6.2.0) > ENHANCEMENT: function resolving should also consider return type > ---------------------------------------------------------------- > > Key: TEIID-235 > URL: https://jira.jboss.org/jira/browse/TEIID-235 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > > Defect Tracker #24030: The use of PreparedStatements will cause functions to sometimes not resolve. However additional type information may be available if the function is used in comparison criteria. In this case the return type may also be used to match the signature of the function. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-235) ENHANCEMENT: function resolving should also consider return type

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-235?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-235: --------------------------------- Assignee: Steven Hawkins > ENHANCEMENT: function resolving should also consider return type > ---------------------------------------------------------------- > > Key: TEIID-235 > URL: https://jira.jboss.org/jira/browse/TEIID-235 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > > Defect Tracker #24030: The use of PreparedStatements will cause functions to sometimes not resolve. However additional type information may be available if the function is used in comparison criteria. In this case the return type may also be used to match the signature of the function. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-235) ENHANCEMENT: function resolving should also consider return type

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-235?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-235. ---------------------------------- Resolution: Done Added by deferring function resolution exceptions until we've had a chance to set a type hint from the surrounding criteria or expression. See TestResolver Will remove the KI from the documentation that recommends using a convert to indicate type. > ENHANCEMENT: function resolving should also consider return type > ---------------------------------------------------------------- > > Key: TEIID-235 > URL: https://jira.jboss.org/jira/browse/TEIID-235 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > > Defect Tracker #24030: The use of PreparedStatements will cause functions to sometimes not resolve. However additional type information may be available if the function is used in comparison criteria. In this case the return type may also be used to match the signature of the function. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-523) hasWsdl attribute Not Set in VDB

by Ted Jones (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-523?page=com.atlassian.jira.plug... ] Ted Jones moved TEIIDDES-139 to TEIID-523: ------------------------------------------ Project: Teiid (was: Teiid Designer) Key: TEIID-523 (was: TEIIDDES-139) Component/s: Common (was: VDB & Execution) Fix Version/s: 6.1.0 (was: 6.1.0) Affects Version/s: 6.0.0 (was: 6.1.0) > hasWsdl attribute Not Set in VDB > -------------------------------- > > Key: TEIID-523 > URL: https://jira.jboss.org/jira/browse/TEIID-523 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.1.0 > > > The hasWsdl attribute of a VDB should be set to true for VDBs that contain a MetaMatrixDataServices.wsdl file. Currently this value is false for Web Service VDBs. This attribute is used for the WSDL auto-discovery process. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-252) Add constant cohersion to rewriter for comparison criteria.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-252?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-252. ---------------------------------- Resolution: Done Added the rewriter checks to setcriteria and compare criteria simplifications. See TestQueryRewriter. > Add constant cohersion to rewriter for comparison criteria. > ----------------------------------------------------------- > > Key: TEIID-252 > URL: https://jira.jboss.org/jira/browse/TEIID-252 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.1.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > From a recent discussion with Larry, it would be good for the rewriter to handle situations like: > "convert(col, type1) = constant of type2" => "col = constant of type1", where type1 is something other than string. > We already have resolver logic to do this and in many circumstance failing to apply the narroring conversion would indicate a failing comparison. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2009