in reply to Re: DBI Invalid Cursor State when PRINT statements are embedded in SQL
in thread DBI Invalid Cursor State when PRINT statements are embedded in SQL
I agree.. I don't use this syntax, it is in a lot of store procs another guy wrote that I am trying to run from Perl.
A DBA sent me this regarding MSSQL PRINT:
The PRINT statement takes either one character or a Unicode string expression as a parameter. It returns the string as a message to the application. The message is returned as an informational error in ADO, OLE DB, and ODBC applications. SQLSTATE is set to 01000, the native error is set to 0, and the error message string is set to the character string specified in the PRINT statement. The string is returned to the message handler call-back function in DB-Library applications.
How can I trap this error and continue? Would this be better as a new question at this point?