Nice meeting you, and thank you for your thoughtful post.
I went ahead and got rid of the SQL type binding, and the program ran along happily.
But this is a workaround.
"...it can usually (although not always) describe them via SQLDescribeParam and it can convert them internally..."
The reason I added the SQL typing in the first place, was because I've encountered a situation where Perl didn't know that the incoming insert was a string, and thought it was an integer (that happens when you have a subroutine in one package, doing the execute_array, and the original call is outside the package).
"...in Perl all your data is string data anyway..."
I have several cases where the table index is an integer, not a string.
Referring to your suggestion:
set DBI_TRACE=DBD=x.log
where is that command entered? at the command line DOS window? and is x.log the filename?
I'll use it next time I hit a DBI/DBD::ODBC error.
Many TIA
Helen
In reply to Re^2: DBI/ODBC error: "Optional feature not implemented (SQL-HYC00)"
by HelenCr
in thread DBI/ODBC error: "Optional feature not implemented (SQL-HYC00)"
by HelenCr
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |