sql - Differences between TdOleDb and Teradata .NET provider -
in converting of our old apps tdoledb provider .net provider, i've discovered number of differences in sql that's supported. 1 of 2 examples i've come across how tdoledb allows this:
substring('abcd',2,2)
the .net provider, however, throws exception. have convert 1 of teradata's 2 supported substring functions this:
substr('abcd',2,2) substring('abcd' 2, 2)
is there way identify known differences in how parser works between these 2 providers? plan on testing everything, miss 1 or 2 sql executions, being able search our apps unsupported sql great help.
edit
here's other example found 2 providers behave differently. old oledb code executing macro commandtype.storedprocedure
:
cmdquote = new oledb.oledbcommand cmdquote.connection = conquote cmdquote.commandtype = commandtype.storedprocedure cmdquote.commandtext = "mydb.mymacro"
when change of oledb classes of .net provider, teradata throws exception:
[teradata database] [5494] 'mymacro' not stored procedure
to work .net provider, have convert this:
cmdquote = new tdcommand cmdquote.connection = conquote cmdquote.commandtext = "execute mydb.mymacro(?)" cmdquote.parameters.add(myparam)
seems oledb supports (at least some) odbc-syntax, see
Comments
Post a Comment