Skip Menu |
 

This queue is for tickets about the DBD-ODBC CPAN distribution.

Report information
The Basics
Id: 43451
Status: resolved
Priority: 0/
Queue: DBD-ODBC

People
Owner: Nobody in particular
Requestors: William.Flynn [...] ftc.usda.gov
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 1.18_4



X-Nai-Spam-Rules: 2 Rules triggered BAD_HDR_SEQ=1, RV3215=0
X-Originalarrivaltime: 19 Feb 2009 23:20:20.0318 (UTC) FILETIME=[A1E817E0:01C992E8]
MIME-Version: 1.0
X-Spam-Status: No, hits=-4.0 required=8.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED
Content-Class: urn:content-classes:message
X-Nai-Spam-Score: 1
X-Virus-Checked: Checked by ClamAV on 16.mx.develooper.com
Message-ID: <C416E6AF07AFC24A9EDD2BAB5D49FFD301817B68 [...] cofortcol2s309.agwest.one.usda.gov>
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C992E8.9DA1800D"
X-MS-Tnef-Correlator:
Received: from la.mx.develooper.com (x1.develooper.com [63.251.223.170]) by diesel.bestpractical.com (Postfix) with SMTP id 150B619B81EE for <bug-DBD-ODBC [...] rt.cpan.org>; Thu, 19 Feb 2009 18:42:04 -0500 (EST)
Received: (qmail 16295 invoked by uid 103); 19 Feb 2009 23:42:04 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 19 Feb 2009 23:42:04 -0000
Received: from ftc-mail-edge1.fsc.usda.gov (HELO ftc-mail-edge1.fsc.usda.gov) (199.141.13.70) by 16.mx.develooper.com (qpsmtpd/0.43rc1) with ESMTP; Thu, 19 Feb 2009 15:42:01 -0800
Received: from (unknown [199.141.13.70]) by DA32USCOFC1_AVS01.usda.gov with smtp id 785e_e6f046b6_fede_11dd_85ee_001143d22fdf; Thu, 19 Feb 2009 23:42:01 +0000
Received: from (unknown [199.141.13.70]) by FTC-MAIL-AV1.FSC.USDA.GOV with smtp id 24dc_e6f128f6_fede_11dd_ac58_001143d33bf3; Thu, 19 Feb 2009 16:41:59 -0700
Received: from COFORTCOL2S300.agwest.one.usda.gov ([199.141.13.200]) by ftc-mail-edge1.fsc.usda.gov (8.13.8/8.13.8) with ESMTP id n1JNKwoU004491 for <bug-DBD-ODBC [...] rt.cpan.org>; Thu, 19 Feb 2009 16:20:59 -0700
Received: from cofortcol2s309.agwest.one.usda.gov ([199.141.13.209]) by COFORTCOL2S300.agwest.one.usda.gov with Microsoft SMTPSVC(6.0.3790.3959); Thu, 19 Feb 2009 16:20:20 -0700
Delivered-To: cpan-bug+DBD-ODBC [...] diesel.bestpractical.com
Subject: Inserting more than 8,000 characters into SQL Server varchar(max) field give "Invalid precision value" error
Return-Path: <William.Flynn [...] ftc.usda.gov>
Thread-Index: AcmS6J2EjjSuttw0QhuQj8eFDi7Iqw==
X-Original-To: bug-DBD-ODBC [...] rt.cpan.org
X-Spam-Check-BY: 16.mx.develooper.com
X-Nai-Spam-Level: *
Date: Thu, 19 Feb 2009 16:20:12 -0700
X-Spam-Level: *
X-MS-Has-Attach:
Thread-Topic: Inserting more than 8,000 characters into SQL Server varchar(max) field give "Invalid precision value" error
X-Mimeole: Produced By Microsoft Exchange V6.5
To: <bug-DBD-ODBC [...] rt.cpan.org>
From: "Flynn, William - Fort Collins, CO" <William.Flynn [...] ftc.usda.gov>
Content-Length: 0
content-type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: us-ascii
Content-Length: 302
Download (untitled) / with headers
text/plain 302b
Broken in 1.18 When trying to insert more than 8,000 characters into a varchar(max) field in a SQL Server database the following error occurs: DBD::ODBC::st execute failed: [Microsoft][ODBC Microsoft Access Driver]Invalid precision value (SQL-HY104) Inserting 8,000 characters or less works fine.
content-type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: us-ascii
Content-Length: 1547
MIME-Version: 1.0
In-Reply-To: <C416E6AF07AFC24A9EDD2BAB5D49FFD301817B68 [...] cofortcol2s309.agwest.one.usda.gov>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <C416E6AF07AFC24A9EDD2BAB5D49FFD301817B68 [...] cofortcol2s309.agwest.one.usda.gov>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-31384-1235658437-278.43451-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 437
Download (untitled) / with headers
text/plain 437b
Apologies for not replying to your bug report sooner. I normally get emails from the rt system when a bug is posted or changed but I have received none recently and did not notice this until I spotted the following thread on perl monks: http://www.perlmonks.org/?node_id=746522 I will try and look in to this in the next few days but I think it may already be fixed. Will get back to you soon. Martin -- Martin J. Evans Wetherby, UK
MIME-Version: 1.0
In-Reply-To: <C416E6AF07AFC24A9EDD2BAB5D49FFD301817B68 [...] cofortcol2s309.agwest.one.usda.gov>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <C416E6AF07AFC24A9EDD2BAB5D49FFD301817B68 [...] cofortcol2s309.agwest.one.usda.gov>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-2264-1236533728-1862.43451-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 853
Download (untitled) / with headers
text/plain 853b
On Thu Feb 19 18:42:22 2009, William.Flynn@ftc.usda.gov wrote: Show quoted text
> Broken in 1.18 > > When trying to insert more than 8,000 characters into a varchar(max) > field in a SQL Server database the following error occurs: > > DBD::ODBC::st execute failed: [Microsoft][ODBC Microsoft Access > Driver]Invalid precision value (SQL-HY104) > > Inserting 8,000 characters or less works fine. > >
Are you using Microsoft native Client? Did make test for DBD::ODBC run to completion without errors? What version of DBD::ODBC are you using? If you are using native client then older versions have a bug which leads to the error you are reporting. Have you updated it to the latest version? When you run make test, it will spot older native clients that are broken. BTW, there is no need to start a new rt for followups. Martin -- Martin J. Evans Wetherby, UK
MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-2264-1236533728-1862.43451-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <C416E6AF07AFC24A9EDD2BAB5D49FFD301817B68 [...] cofortcol2s309.agwest.one.usda.gov> <rt-3.6.HEAD-2264-1236533728-1862.43451-0-0 [...] rt.cpan.org>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-25907-1237042699-708.43451-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 596
Download (untitled) / with headers
text/plain 596b
On Sun Mar 08 13:35:28 2009, MJEVANS wrote: Show quoted text
> On Thu Feb 19 18:42:22 2009, William.Flynn@ftc.usda.gov wrote:
> > Broken in 1.18 > > > > When trying to insert more than 8,000 characters into a varchar(max) > > field in a SQL Server database the following error occurs: > > > > DBD::ODBC::st execute failed: [Microsoft][ODBC Microsoft Access > > Driver]Invalid precision value (SQL-HY104) > > > > Inserting 8,000 characters or less works fine. > > > >
I believe this is working in at least 1.18_4 so I'm marking this fixed unless you tell me otherwise. Martin -- Martin J. Evans Wetherby, UK


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.