lt.aspx?scid=kb;en-us;140696
>
> Tite: INF: RAISERROR, PRINT, and the MS SQL Server ODBC Driver
>
> -Original Message-
> From: Moosmann, James
> Sent: Tuesday, October 19, 2004 4:54 PM
> To: '[EMAIL PROTECTED]'
> Cc: [EMAIL PROTECTED]
> Subject: RE: Inval
D]
Subject: RE: Invalid cursor state when using PRINT in MSSQL
I tried that... didn't work.
I found this MS article on the problem: I kind of suspect it is in how
DBD-ODBC implements its calls SQLExecDirect() and the subsequent call to
SQLError(). The article seems to imply that the timi
James
Cc: [EMAIL PROTECTED]
Subject: RE: Invalid cursor state when using PRINT in MSSQL
James
I'm an Oracle not a Sybase or SQL Server person, but I believe that you can
connect to SQL Server using Free TDS and DBD::Sybase
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject:RE: Invalid cursor state when using PRINT in MSS
: Moosmann, James
Subject: RE: Invalid cursor state when using PRINT in MSSQL --- TRACE
AND SCRIPT ENCLOSED
James,
CC'ing dbi-user since this is where you posted first.
Basically you are stuffed. I analysed your log and did the same thing in
ODBCTest which used to come with MDAC and it fails i
James,
CC'ing dbi-user since this is where you posted first.
Basically you are stuffed. I analysed your log and did the same thing in
ODBCTest which used to come with MDAC and it fails in the same way:
SQLPrepare(print 's' select count(*) from table print 'e')
SQLNumResultCols()
returns SQL_ER
Martin,
Thanks for the reply.
Before I do that, I will try finding the version of DBD and DBI that you are
using. From my original post I am using DBD 1.07 and DBI 1.43.
>[EMAIL PROTECTED] /tmp]$ perl -e 'use DBD::ODBC; print $DBD::ODBC::VERSION;'
>1.11
>[EMAIL PROTECTED] /tmp]$ perl -e 'use D
t;
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 18, 2004 11:47 PM
> To: Moosmann, James
> Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Subject: RE: Invalid cursor state when using PRINT in MSSQ
smann, James
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Subject: RE: Invalid cursor state when using PRINT in MSSQL
James
if you think it's a DBD::ODBC issue, why not use DBD::Sybase instead?
Dan
"Moosmann, James" <[EMAIL PROTECTED]>
D]'" <[EMAIL PROTECTED]>, (bcc: Dan
Horne/IT/AKLWHG/WHNZ)
Subject:RE: Invalid cursor state when using PRINT in MSSQL
Jeff,
It is VERY VALID syntax for both MSSQL ... AND.. Sybase. I have been
coding
in Perl and DBI for several years now and I am NOT trying to use
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, October 18, 2004 9:08 PM
To: Moosmann, James
Cc: '[EMAIL PROTECTED]'
Subject: Re: Invalid cursor state when using PRINT in MSSQL
my $sql = qq#
PRINT 'starting select'
select count(*) from anytabl
___
"Moosmann, James" <[EMAIL PROTECTED]>
10/18/2004 06:46 PM
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject:Invalid cursor state when using PRINT in MSSQL
I am using DBI and DBD-ODBC to
I am using DBI and DBD-ODBC to connect to an MSSQL Server and this query
gets an invalid cursor state:
PRINT 'starting select'
select count(*) from anytable
PRINT 'finished'
If I only run the PRINT command... it works.
If I run the full query against a sybase server... only the top select
prints
13 matches
Mail list logo
