Yuriy Kaminskiy
2011-10-14 16:57:56 UTC
According to DBI documentation:
The data type is 'sticky' in that bind values passed to execute() are bound
with the data type specified by earlier bind_param() calls, if any.
Portable applications should not rely on being able to change the data type
after the first C<bind_param> call.
It seems not work as described above with DBD::SQLite.
This also completely breaks
bind_param_array($n, [@vals], $sql_type);
(as it uses bind_param($n, undef, $sql_type) once to assign type);
Attached patch fixes this problem; includes regression test and update to broken
t/rt_71311_bind_col_and_unicode.t
The data type is 'sticky' in that bind values passed to execute() are bound
with the data type specified by earlier bind_param() calls, if any.
Portable applications should not rely on being able to change the data type
after the first C<bind_param> call.
It seems not work as described above with DBD::SQLite.
This also completely breaks
bind_param_array($n, [@vals], $sql_type);
(as it uses bind_param($n, undef, $sql_type) once to assign type);
Attached patch fixes this problem; includes regression test and update to broken
t/rt_71311_bind_col_and_unicode.t