[
https://issues.jboss.org/browse/TEIID-2565?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2565.
-----------------------------------
Assignee: Steven Hawkins (was: Ramesh Reddy)
Fix Version/s: 8.4.1
8.5
Resolution: Done
Added length as an option to the object type. Also the char type should really not
support length (it has to be 1), but that was left alone.
Problem with DDL returned via admin api - column has erroneous
datatype
-----------------------------------------------------------------------
Key: TEIID-2565
URL:
https://issues.jboss.org/browse/TEIID-2565
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 8.4
Reporter: Mark Drilling
Assignee: Steven Hawkins
Fix For: 8.4.1, 8.5
Deployed a greenplum datasource, then deployed a dynamic vdb and did a getSchema via the
admin api. One of the tables in the ddl contains a column as shown in the following ddl
snippet:
CREATE FOREIGN TABLE "gp_toolkit.gp_log_command_timings" (
logduration object(49) OPTIONS (NAMEINSOURCE '"logduration"',
NATIVE_TYPE 'interval')
) OPTIONS (NAMEINSOURCE
'"gp_toolkit"."gp_log_command_timings"', UPDATABLE TRUE);
The logduration type of object erroneously has a length.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira