It turns out an optimization I made in 1.24_2 causes problems and
ultimately leads to rebinding columns unnecessarily and leaking memory.
1.26_3 fixes this problem (thanks to Steve Bentley for spotting this).
If you are using a development release of DBD::ODBC you are strongly
recommended to upgrade. If you are using 1.25 in a daemon process the
decision is a little more complicated as the 1.26 series introduces a
large number of changes for ODBC 3.0 compatibility. Basically my
recommendations are:
o if you are using 1.24 in production stay with it but test 1.26_3
seperately
o if you using 1.24_2 or above either downgrade to 1.24 or upgrade to
1.26_3. If you hit an ODBC 3.0 issue in 1.26_3 downgrade to 1.24_1 and
report the issue to me or you'll suffer again when 1.26 development
releases are released officially as 1.27.
I am sorry for this inconvenience but given the lack of testing with
real ODBC drivers (instead of smoke testing in Perl which mostly just
says the Makefile.PL is ok) this sometimes happens.
Many thanks to Steve for spotting this.
Martin
