On Mon, Sep 18, 2006 at 10:30:49PM -0400, Sam Tregar wrote:
On Mon, 18 Sep 2006, Tim Bunce wrote:
Yes, and the same applies to AutoCommit. Whether it's a good thing or
not is debatable but it's been that way forever. The 'workaround' is
to explicitly state the attributes you want.
Hmmm,
I realize that this is very specific to the database, however, it may be
possible to set a resource limit at the database level that will prevent
the queries from consuming too much time.
Chuck
[EMAIL PROTECTED] wrote:
On Sep 18, 2006, at 6:18 PM, Tyler MacDonald wrote:
Dean Arnold [EMAIL
Hi,
Back in March this year Jonathan Gillespie reported the following
error in DBD::ODBC test suite:
Can't change param 1 maxlen (51-50) after first bind at
t/20SqlServer.t line 180.
(see http://www.mail-archive.com/dbi-users@perl.org/msg26946.html).
The same version of DBI and DBD::ODBC works
And some drivers have a timeout parameter that handles this issue at the
vendor API level (e.g. DBD::Sybase's timeout parameter that is handled
internally by OpenClient).
Michael
Extranet
[EMAIL PROTECTED] - 19.09.2006 15:37
To: henri
cc: tyler, darnold, Tim.Bunce, dbi-users,
On Tue, 19 Sep 2006 [EMAIL PROTECTED] wrote:
And some drivers have a timeout parameter that handles this issue at the
vendor API level (e.g. DBD::Sybase's timeout parameter that is handled
internally by OpenClient).
Good to know. I'm looking into adding something like this to MySQL,
but
On Tue, Sep 19, 2006 at 02:47:18PM +0100, Martin J. Evans wrote:
Hi,
Back in March this year Jonathan Gillespie reported the following
error in DBD::ODBC test suite:
Can't change param 1 maxlen (51-50) after first bind at
t/20SqlServer.t line 180.
(see
On 19-Sep-2006 Tim Bunce wrote:
On Tue, Sep 19, 2006 at 02:47:18PM +0100, Martin J. Evans wrote:
Hi,
Back in March this year Jonathan Gillespie reported the following
error in DBD::ODBC test suite:
Can't change param 1 maxlen (51-50) after first bind at
t/20SqlServer.t line 180.
(see
Martin J. Evans wrote:
On 19-Sep-2006 Tim Bunce wrote:
On Tue, Sep 19, 2006 at 02:47:18PM +0100, Martin J. Evans wrote:
I never really
got to the root of the problem but it appears:
in dbdimp.c did a:
svGrow(phs-sv, 50+1)
but
SvLEN(phs-sv) returns 52!
DBD::ODBC does not expect this so the
On 19-Sep-2006 Steve Hay wrote:
Martin J. Evans wrote:
On 19-Sep-2006 Tim Bunce wrote:
On Tue, Sep 19, 2006 at 02:47:18PM +0100, Martin J. Evans wrote:
I never really
got to the root of the problem but it appears:
in dbdimp.c did a:
svGrow(phs-sv, 50+1)
but
SvLEN(phs-sv) returns 52!
Attached is a patch which fixes the problem in t/20SqlServer.t in
DBD::ODBC 1.13 (patch actually against latest subversion) which causes:
Can't change param 1 maxlen (51-50) after first bind at
t/20SqlServer.t line 180.
As Steve writes below, SvGROW was changed to allocate up to the
next long
10 matches
Mail list logo