Archives of the TeradataForum
Message Posted: Fri, 21 Jan 2011 @ 20:47:16 GMT
This is for the TTU savvy folks that contribute to the forum.
We have noticed that some of the ODBC scalar functions in TTU13 ODBC are not working, specifically RTRIM and LTIRM.
In TTU 12 in SQL Assistant there was the Allow use of ODBC SQL Extension checkbox in the application, and you can use that to control whether or not the application will support them.
However, in TTU13 SQL assistant there is no such option when connecting with ODBC. Also, the documentation for TTU 13 SQL assistant does not mention the omission of this feature.
ETL Tools that use ODBC connectors are failing as well when people try to use these functions with the TTU13 ODBC driver ,whereas they succeed with the TTU12 ODBC driver with seemingly similar (as identical as possible) settings.
I have dug through the manuals (12 and 13) and cant find the ODBC setting that enables or disables the extensions, is there one?
Before I get flamed for allowing non-standard SQL, which I don t condone at all , I really just want to understand if this merits a bug, or if some features were silently dropped or are now deprecated.
A few obvious workarounds are:
1.) Fix the bad SQL
2.) Compile Ltrim, Rtrim functions as UDFs.
But I have a few questions still.
1.) Has anyone experienced something similar?
2.) Is there a setting in the ODBC drivers that needs to be enabled disabled so that it will allow the use of the ODBC extensions?
3.) Should ODBC functions work in a default manner, with nothing to set to allow them?
Eric W. Barner
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|