I have a fix for this but it only applies to version 16 and above. Teradata added a new table in version 16 called DBC.columnsq which lets you extract the view column information using our current query extract structure. For versions less than 16 we will have to do a "help column VIEWNAME.*" and extract the column information. This doesn't match our current query column structure so will have to change code to capture the data. I have not tested this yet.
Added support for Teradata V16
V19 SVN# 55911
V19.5 SVN# 55912
Added support for Teradata V16
V19 SVN# 55911
V19.5 SVN# 55912
Verified in ADS 19.0.1-6 for Vertica 16.
The problem is still reproducible in Vertica 15.
Verified in ADS 19.0.1-6 for Vertica 16.
The problem is still reproducible in Vertica 15.
Added option to shutoff QVCI for Teradata V16. We will attempt to use Help Column to retrieve view column information.
V20 SVN# 56898
Added option to shutoff QVCI for Teradata V16. We will attempt to use Help Column to retrieve view column information.
V20 SVN# 56898
Issue #15610 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
No fixed build |
No time estimate |
I have a fix for this but it only applies to version 16 and above. Teradata added a new table in version 16 called DBC.columnsq which lets you extract the view column information using our current query extract structure. For versions less than 16 we will have to do a "help column VIEWNAME.*" and extract the column information. This doesn't match our current query column structure so will have to change code to capture the data. I have not tested this yet.