Archives of the TeradataForum

Message Posted: Tue, 02 Sep 2003 @ 15:27:13 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

We've had a lot of users trip over this kind of problem lately. The ODBC standard includes functions that are automatically mapped from an ODBC syntax to the correct host syntax. The problem is that the functions are supposed to be enclosed in a special syntax and the NCR driver is translating them when they appear in clear text.

For example:

select user, length(user), characters(user);

If you look at the column headings you'll see that "length" has been translated to "characters".

This is an ODBC event, which you can prove by going to Tools/Options/Query and unchecking the 'Allow use of ODBC SQL Extensions in queries' box. Rerunning the query generates a 3707 Syntax error message. Remember to recheck the box after the test: stored procedures won't work from Queryman without it.

We've also had past problems with the ODBC date form "{d 'yyyy-mm-dd'}", which is sometimes generated by 3rd party tools. Even though this form works with EXPLAIN, it fails with SHOW:

select {d '2003-09-02'};

With current releases I think the date issue with SHOW is fixed, but the function substitution is still being coded.

/dave hough

	<Prev	Next>		<<First	<Prev	Next>	Last>>