Skip Menu |
 

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

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

People
Owner: Nobody in particular
Requestors: melazyboy [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: 1.17_3



Subject: FAQ
Download (untitled) / with headers
text/plain 193b
please answer the question: Why do I get invalid value for cast specification (22018) from SQL Server when inserting with parameters? on the FAQ. it is currently a big tease for the googlebot.
Download (untitled) / with headers
text/plain 189b
of course the answer is an invalid cast, a popular one is probably for the MS SQL type 'bit'. The version of this module no longer accepts 'True' (if it ever did). Instead it requires 1/0.
Download (untitled) / with headers
text/plain 690b
On Fri Dec 12 19:11:54 2008, ECARROLL wrote: Show quoted text
> of course the answer is an invalid cast, a popular one is probably for > the MS SQL type 'bit'. > > The version of this module no longer accepts 'True' (if it ever did). > Instead it requires 1/0.
I don't believe DBD::ODBC ever accepted 'True' as it would have had to do something special with it. DBD::ODBC binds most columns as strings and lets the ODBC driver do the conversion so if 'True' used to work and does not now then I'd suggest the ODBC driver changed. Anyway, thank you for pointing out the answer for this question had got lost. I have reinstated it for the next release of DBD::ODBC. 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.