February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-7) Control of BigDecimal precision and scale

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-7?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-7: ----------------------------- Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x Affects: [Compatibility/Configuration, Release Notes] (was: [Release Notes, Compatibility/Configuration]) > Control of BigDecimal precision and scale > ----------------------------------------- > > Key: TEIID-7 > URL: https://jira.jboss.org/jira/browse/TEIID-7 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Jerry Helbling > Priority: Minor > Fix For: 6.1.0 > > > Problem 1: The parser defaults to parsing literals that look like bigdecimal as doubles, which have no scale. > Workaround (which is on devcentral): You can avoid the above conversions by wrapping the values in a convert in the query (example: "convert('123.00', BigDecimal )"). > A better fix is update the parser to look for loss of scale information and to use the bigdecimal type instead. > Problem 2: default division behavior JBEDSP-305 > Problem 3: No explicit control via the parser > It would be good to provide explicit precision and scale via "convert(xxx, BigDecimal(10, 2))" - side note bigdecimal is a bad name for this type. it should really just be decimal > Reference: This is related to Issue Tracker Issue 175485. -- 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-6) Change Enterprise Web Services and SQLQueryWebService to allow Encypted SOAP Messages

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-6?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-6: ----------------------------- Component/s: SOAP Services Fix Version/s: 6.x Affects Version/s: 6.x > Change Enterprise Web Services and SQLQueryWebService to allow Encypted SOAP Messages > ------------------------------------------------------------------------------------- > > Key: TEIID-6 > URL: https://jira.jboss.org/jira/browse/TEIID-6 > Project: Teiid > Issue Type: Bug > Components: SOAP Services > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 6.x > > > Defect Tracker #24277: Need to change our dataservice and SQWS to use encrypted SOAP messages instead of PasswordText. PasswordText is ok if SSL is used, but some customers may prefer not to use SSL. -- 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-5) When JChannel is in connected state, JBoss Cache fails to register itself as the co-ordinator

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-5?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-5: ----------------------------- Component/s: Server Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > When JChannel is in connected state, JBoss Cache fails to register itself as the co-ordinator > --------------------------------------------------------------------------------------------- > > Key: TEIID-5 > URL: https://jira.jboss.org/jira/browse/TEIID-5 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.0.0 > > > If JBoss cache when in replicated mode, and is supplied with JChannel which is already in the connected state, it fails to register it self as the co-ordinator, hence hangs. Will also submit a JIRA to JBoss Cache team. -- 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-4) Remove Redundant Jars from Axis2 Project

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-4?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4: ----------------------------- Component/s: SOAP Services Fix Version/s: 6.x Affects Version/s: 6.x > Remove Redundant Jars from Axis2 Project > ---------------------------------------- > > Key: TEIID-4 > URL: https://jira.jboss.org/jira/browse/TEIID-4 > Project: Teiid > Issue Type: Bug > Components: SOAP Services > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Ted Jones > Priority: Minor > Fix For: 6.x > > > Defect Tracker #24217: Redundant jars should be removed from the Axis2 project and picked up from the appropriate project in the workspace. -- 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-3) Allow connectors to specify function capability for specific type signature

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-3?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3: ----------------------------- Component/s: Misc. Connectors Fix Version/s: 6.x Affects Version/s: 6.x > Allow connectors to specify function capability for specific type signature > --------------------------------------------------------------------------- > > Key: TEIID-3 > URL: https://jira.jboss.org/jira/browse/TEIID-3 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.x > > > Defect Tracker #15144: Connectors should be able to specify pushdown capability for particular type signatures of a function. We have seen several cases where this would be helpful. This can probably be done without changing current Connector API by allowing the ConnectorCapabilities function method to return method signatures instead of just function names. For example, "mod(integer, integer)" instead of just "mod". Needs some further design still. -- 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-2) Fix for NPE in isSuperUser method.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-2?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2: ----------------------------- Component/s: Console Affects Version/s: 6.0.0 > Fix for NPE in isSuperUser method. > ---------------------------------- > > Key: TEIID-2 > URL: https://jira.jboss.org/jira/browse/TEIID-2 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Reporter: Jerry Helbling > Assignee: Jerry Helbling > Priority: Minor > > Refer to internal case 226138. -- 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-141) Develop a strategy for backtracking during planning

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-141?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-141: ------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Develop a strategy for backtracking during planning > --------------------------------------------------- > > Key: TEIID-141 > URL: https://jira.jboss.org/jira/browse/TEIID-141 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.x > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently rule raise access is run after rule push criteria, which can cause non-pushable criteria to end up in undesirable points of the plan. It would be good to either run rule raise access before the first run of push select criteria, or allow rule raise access to detect what nodes it can "push up". -- 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 February 2009