On 27-Jun-2005 Daniel Kasak wrote:
Jeff Urlwin wrote:
Please read DBD::ODBC pod. Specifically the section on the odbc_cursortype.
Jeff
I just added odbc_cursortype= DBI::SQL_CURSOR_DYNAMIC to our
connection string, and that didn't help things at all.
Martin J. Evans ( see other
Martin J. Evans wrote:
Just tried that. Doesn't seem to have any effect on my system. Here's
the line I added right after create $dbh :
$dbh-{odbc_SQL_ROWSET_SIZE} = 2;
Didn't you say something about using FreeTDS? If so that hack might not work
for FreeTDS. Against MS SQL Server ODBC
Jeff Urlwin wrote:
Please read DBD::ODBC pod. Specifically the section on the odbc_cursortype.
Jeff
I just added odbc_cursortype= DBI::SQL_CURSOR_DYNAMIC to our
connection string, and that didn't help things at all.
Martin J. Evans ( see other post on topic ) says that this won't work
Please read DBD::ODBC pod. Specifically the section on the odbc_cursortype.
Jeff
-Original Message-
From: Daniel Kasak [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 22, 2005 1:22 AM
To: Jeff Urlwin; dbi-users@perl.org
Subject: Re: Attempt to initiate a new SQL Server operation
Daniel,
On 22-Jun-2005 Daniel Kasak wrote:
Martin J. Evans wrote:
As far as I am aware this is a limitation of the TDS protocol used and
your example code will not work unless you force a server-side cursor (see
DBD::ODBC pod and look for odbc_SQL_ROWSET_SIZE but I warn you that you
really
As far as I am aware this is a limitation of the TDS protocol used and
your example code will not work unless you force a server-side cursor (see
DBD::ODBC pod and look for odbc_SQL_ROWSET_SIZE but I warn you that you really
will need to close everything i.e. force SQLFreeStmt(SQL_CLOSE) or you
Hi,
You should only have to clear the statement if you are fetching a single
row or fetching into a set variables. This will happen even if the
result set on the backend contains only one record. If you are fetching
row by row in a loop, fetching one more time beyond the last record
should
Terence,
I could be wrong but from what little I remember from TDS I think
that unless you enable a server-side cursor, once you start retrieving
data from the server you have no choice but to keep reading it until
it is exhausted - this is why SQL Server ODBC driver only supports
1 active
Martin J. Evans wrote:
As far as I am aware this is a limitation of the TDS protocol used and
your example code will not work unless you force a server-side cursor (see
DBD::ODBC pod and look for odbc_SQL_ROWSET_SIZE but I warn you that you really
will need to close everything i.e. force
Jeff Urlwin wrote:
Hi all.
I've just ( barely ) managed to get DBD::ODBC == UnixODBC
== FreeTDS
working on my system.
I took a Perl-Gtk2 app which has been running fine, and
substituted the
old DBD::Sybase connection with the DBD::ODBC one, and then
discovered I
could only run one query
Hi all.
I've just ( barely ) managed to get DBD::ODBC == UnixODBC == FreeTDS
working on my system.
I took a Perl-Gtk2 app which has been running fine, and substituted the
old DBD::Sybase connection with the DBD::ODBC one, and then discovered I
could only run one query on SQL Server, and then
Hi all.
I've just ( barely ) managed to get DBD::ODBC == UnixODBC
== FreeTDS
working on my system.
I took a Perl-Gtk2 app which has been running fine, and
substituted the
old DBD::Sybase connection with the DBD::ODBC one, and then
discovered I
could only run one query on
12 matches
Mail list logo
