Actually, the default bind type was 12 (SQL_VARCHAR) in versions .39 and
below.
If you read the POD documentation, you will see that setting it to 0 tells
DBD::ODBC to try to ask the driver itself which type should be for binding.
I believed that this would be an improvement for *most* users. Note that
using EasySoft's pridge and MS SQL Server 2000, everything is fine. I
suggest you see how DirectTechnologies handles SQLDescribeParam as I believe
it's not doing it correctly.
Jeff
>
>
> Hello,
>
> I use DBD::ODBC and DirectTechnologies ODBC Client driver for connecting
> a MS SQL SERVER 2000.
>
> w/ DBD::ODBC 0.39 I haven't got any problems but w/ 0.41 I run into
> trouble, after setting:
>
> $dbh->{odbc_default_bind_type} = 1;
>
> everything is fine.
>
> Why has the default value changed in version 0.40?
>
> Stefan
>
