Archives of the TeradataForum
Message Posted: Thu, 12 Jul 2007 @ 09:42:58 GMT
Good; but do check the UDF as well. I think the following scenario is possible:
1. Somebody creates a UDF called LENGTH.
2. BTEQ fails because the function has certain requirements on argument data type and those requirements are not met in the statement.
3. ODBC driver translates LENGTH to CHARS before it even checks whether there is a UDF with the same name, so no failures but potentially a different query is being executed. Because the UDF's definition of LENGTH could be something totally different from CHARS.
I don't have time to test all this but I thought the scenario above could actually occur. Your error message does strike me as very different from the usual in such cases vague "incorrect syntax" messages (like "expected something between A and B").
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|