 |
 |
Archives of the TeradataForum
Message Posted: Fri, 30 Jul 2004 @ 11:36:48 GMT
| Subj: | | Re: ODBC functions and Teradata SQL. |
| |
| From: | | Victor Sokovin |
| | See the "ODBC 2.0 Reference Guide and SDK", Ch. 14 "Processing an SQL Statement" and Appendix F "Scalar Functions" for more
information. Sorry, but I don't have the ODBC 3.0 references available. | |
That was an interesting reference for me; thanks for posting it. It dates back to 1996 and that was long before I started working with TD. I
now better understand where you are coming from.
When I looked at the list of functions in 2.0 I was surprised how much useful stuff was there, especially in the area of string
manipulation and dates / times. Were all of them really implemented in 2.0 (I doubt ...)? As far as the number of built-in functions is concerned,
3.0 looks really on the low-budget side by comparison.
| | RECAUZR6H / DR68180 addresses the mishandling of ODBC extensions to SQL by the Teradata ODBC driver. At last report, the fixes are
planned for inclusion in TTU 8.0. The ODBC extension syntax looks like: | |
| | in specific. The Teradata driver is not requiring the escape characters in all cases (length, left, right, and others), and allows, for
example, a simple length(mycol) to pass syntax. | |
What is the intention of this change request? Will BTEQ in some future release be able to intelligently convert ODBC escaped functions to
native functions? If not, then we will only have to type more characters in Queryman et al but the code will still be foreign to BTEQ (I
understand that is your main concern). Am I missing something?
Regards,
Victor
| |
