[JBoss JIRA] Created: (TEIID-739) JDBC Connector updates
by Steven Hawkins (JIRA)
JDBC Connector updates
----------------------
Key: TEIID-739
URL: https://jira.jboss.org/jira/browse/TEIID-739
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector
Affects Versions: 6.2.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
The PostgreSQL translator should assume the use of a 8.0 jdbc client (supports back to the 7.2 server) so that we can remove DatePartFunctionModifer/ModifiedDatePartFunctionModifer also support for the bit functions should be added.
The SQL Server translator / capabilities should be updated to assume the use of a 2005, DataDirect, or later driver (all support back to sql server 2000) so that support for most of the time functions can be added.
--
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, 4 months
[JBoss JIRA] Created: (TEIID-741) SQL Server type hadling issues
by Steven Hawkins (JIRA)
SQL Server type hadling issues
------------------------------
Key: TEIID-741
URL: https://jira.jboss.org/jira/browse/TEIID-741
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 6.2.0
If we pushdown a convert(stringvalue, char) function, it turns into the source expression convert(char, stringvalue), which has the following problems: it defaults to type char(30) which is right padded, it is not trimmed since the target type was Char and the trim logic looks only for String. Also it does not account for empty string mapping to null.
The SQL Server tinyint type is unsigned. Our import needs to be modified to this to short, since our byte type is unsigned. Pushing down a convert(numericvalue, byte) as convert(tinyint, numericvalue) is problematic if the byte values are stored in a signed manner.
--
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, 4 months
[JBoss JIRA] Created: (TEIID-803) The connector binding name assigned when created in the designer is not the name in the ConnectorBinding when using AdminAPI
by Van Halbert (JIRA)
The connector binding name assigned when created in the designer is not the name in the ConnectorBinding when using AdminAPI
----------------------------------------------------------------------------------------------------------------------------
Key: TEIID-803
URL: https://jira.jboss.org/jira/browse/TEIID-803
Project: Teiid
Issue Type: Bug
Components: AdminApi, Tools
Affects Versions: 6.2.0
Reporter: Van Halbert
Assignee: Steven Hawkins
The name I assigned to the connectorbinding in the designer was "datasource1". I looked at the advanced properties and there is no other name property defined. Open the vdb file and view the Configuration.def file and it has the following:
<Connector Name="datasource1" ComponentType="Loopback Connector" routingUUID="mmuuid:66dfa66b-4572-46ba-a477-8b6fe3895072">
<Properties>
<Property Name="DeployedName">Transaction_1.datasource1</Property>
</Properties>
</Connector>
When using the adminapi and calleding getName() on ConnectorBinding, the name returned is "Transaction_1.datasource1". The name that the user assignes to the binding should match the getName().
--
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, 4 months