|
Archives of the TeradataForumMessage Posted: Mon, 24 Jan 2011 @ 15:23:17 GMT
Thanks Mike this is good to know. Our particular issue was not specifically with SQL Assistant and it actually turned out to be a strange bug in the ODBC driver. Having to do with the parsing of these ODBC Scalar functions. When using Ltrim/Rtrim , if the query uses an Alias or other Scalar Function keyword subsequent to the functions (i.e. USER in this case) it breaks. Teradata has opened a DR on this. I thought I should share the nature of the issue with everyone, as it is kind of painful to deal with, and it is good FYI. TD Response: "We now isolated/narrowed it down to the word/token "USER_", the ODBC Driver rejects it. Changing it to USR_GROUP_TYPE_XXXX as shown below the query works. This is your workaround. The other is to usr TRIM just for this particular query." Original Query : SELECT USER_GROUP_TYPE.USER_GROUP_TYPE_ID USER_GROUP_TYPE_ID, LTRIM(RTRIM(USER_GROUP_TYPE.USER_GROUP_TYPE_NAME)) AS USER_GROUP_TYPE_NAME FROM USER_GROUP_TYPE ORDER BY USER_GROUP_TYPE_NAME,USER_GROUP_TYPE_ID; Workaround Query: SELECT USER_GROUP_TYPE.USER_GROUP_TYPE_ID AS USR_GROUP_TYPE_ID, LTRIM(RTRIM(USER_GROUP_TYPE.USER_GROUP_TYPE_NAME)) AS USR_GROUP_TYPE_NAME FROM USER_GROUP_TYPE ORDER BY USER_GROUP_TYPE_NAME,USER_GROUP_TYPE_ID Eric W. Barner
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||