February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-358) Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing

by Paul Nittel (JIRA)

Quick Start Guide / Examples needs to add derbyclient.jar to UDFs for previewing -------------------------------------------------------------------------------- Key: TEIID-358 URL: https://jira.jboss.org/jira/browse/TEIID-358 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 6.0.0 Environment: fedora 10 Reporter: Paul Nittel Assignee: Steven Hawkins I ran into this while assisting user Bribek. When the Derby source is created and imported, a connector binding is built in the Designer. The one thing Designer does not do is place the jar file where it needs to be for previewing. The Quick Start Example needs to add the step of adding the derbyclient.jar file using the UDFs view and "Import UDF Extension Jar Files" action. IMHO, the Quick Start needs to be revisited to determine exactly what the required minimum effort is for a user to get through this. Perhaps on the Teiid side avoid all modeling and add a Quick Start on the Designer side that builds the VDB. If Teiid can do the Quick Start with just a VDB, that might be preferable. -- 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

13 years, 10 months

5
9
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, 1 month

1
7
0 / 0

[JBoss JIRA] Created: (TEIID-381) Migrate Teiid JOPR Plugin from Product to Project

by Ted Jones (JIRA)

Migrate Teiid JOPR Plugin from Product to Project -------------------------------------------------- Key: TEIID-381 URL: https://jira.jboss.org/jira/browse/TEIID-381 Project: Teiid Issue Type: Task Components: Build/Kits Reporter: Ted Jones Assignee: Ted Jones Fix For: 6.0.0 The Teiid JOPR Plugin source currently resides on the project side. It needs to be moved to project and incorporated into the TEIID build 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

14 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (TEIID-350) Add documentation about function determinism

by Steven Hawkins (JIRA)

Add documentation about function determinism -------------------------------------------- Key: TEIID-350 URL: https://jira.jboss.org/jira/browse/TEIID-350 Project: Teiid Issue Type: Quality Risk Components: Documentation Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 Functions are given varying levels of determinism, which effect when they are evaluated. Something about this and the effected functions should be added to the docs. -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode

by Greg Haber (JIRA)

MySQL connector assumes that database is running in ANSI mode rather than the default mode ------------------------------------------------------------------------------------------ Key: TEIID-379 URL: https://jira.jboss.org/jira/browse/TEIID-379 Project: Teiid Issue Type: Bug Components: JDBC Connector Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern Reporter: Greg Haber Assignee: Steven Hawkins I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume that it is connecting to a MySQL database running in "ANSI" SQL mode For instance, we list in the capabilities class that MySQL supports || as a string concatenation parameter, but it actually only supports it if the SQL mode "PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set when you set the "ANSI" meta-mode (see http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details). This is a bad assumption as it is not the default setting for MySQL (the default sql-mode setting is "", or no special modes). I took a look at some of the databases used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that they have sql-mode set to ANSI on the server side. I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix code in this regard, so Teiid has the same issue. Two possible resolutions are: -Rework the connector to remove any assumptions that sql-mode=ANSI -set sql-mode to ANSI when establishing new connections to MySQL (this can be done by sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a connection). Unfortunately there does not appear to be a way to set this mode via a JDBC connection property - you need to send the "set" command after establishing the 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

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-386) Improve error reporting to NOT include stack traces when appropriate and logging level < Detail

by Paul Nittel (JIRA)

Improve error reporting to NOT include stack traces when appropriate and logging level < Detail ----------------------------------------------------------------------------------------------- Key: TEIID-386 URL: https://jira.jboss.org/jira/browse/TEIID-386 Project: Teiid Issue Type: Feature Request Components: Query Engine Environment: Any and all Reporter: Paul Nittel Assignee: Steven Hawkins The server presently adds stack traces with reckless abandon. It seems like anything that upsets the software yields at least one stack trace. I'd like to propose that "human errors", like parsing SQL statements, return just an error (in the logs, too). If the server is set to log at Detail or Trace, then crank out the stack traces if that's necessary. Logs that show only important stuff are more valuable. (I looked in Teiid and didn't see an entry like this. If it's a dup, that's fine, as long as the stack trace deluge is remedied.) -- 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

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-346) Add back 5.5 connector api with bridge logic

by Steven Hawkins (JIRA)

Add back 5.5 connector api with bridge logic -------------------------------------------- Key: TEIID-346 URL: https://jira.jboss.org/jira/browse/TEIID-346 Project: Teiid Issue Type: Sub-task Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.1.0 To support 5.5 connectors, we need to add back the old com.metamatrix.data api. -- 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

[JBoss JIRA] Created: (TEIID-356) Oracle sequence insert override change

by Steven Hawkins (JIRA)

Oracle sequence insert override change -------------------------------------- Key: TEIID-356 URL: https://jira.jboss.org/jira/browse/TEIID-356 Project: Teiid Issue Type: Sub-task Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 The current behavior is to replace existing insert values if the column appears to be a sequence. This is a hack and prevents the proper usage of an overriding insert value. The new behavior will look for the sequence name in source only if a value is not supplied and the column is marked as auto_increment. This is a breaking changes that needs to be highlighted in the release notes. -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIID-352) JDBC SQLTranslator issues

by Steven Hawkins (JIRA)

JDBC SQLTranslator issues ------------------------- Key: TEIID-352 URL: https://jira.jboss.org/jira/browse/TEIID-352 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 SQLTranslators are extremely cumbersome and not well documented. We need something much more like Hibernate's dialect. Also the time literal for Access/SQLServer is incorrect and the limit with set op will also fail for Access/SQLServer. -- 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
4
0 / 0

[JBoss JIRA] Created: (TEIID-345) Consolidate ifnull, nvl, and coalesce support

by Steven Hawkins (JIRA)

Consolidate ifnull, nvl, and coalesce support --------------------------------------------- Key: TEIID-345 URL: https://jira.jboss.org/jira/browse/TEIID-345 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 We should use ifnull to represent the 2 arg function form and coalesce to represent the n arg (not available until var arg support). The rewriter should rewrite nvl as ifnull and connectors should express support for ifnull and coalesce only. -- 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
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009