Set this before execute to "force" DBD:: ODBC to re-obtain the result set's number of columns and column types for each execute.
Especially useful for calling stored procedures which may return different result sets each execute.
DBD:: ODBC - ODBC Driver for DBI This documentation refers to DBD:: ODBC version 1.52.
This version of DBD:: ODBC contains a significant fix to unicode when inserting into CHAR/VARCHAR columns and it is a change in behaviour from 1.45.
This means so long as your database can store the data you are inserting, when you read it back you should get what you inserted. DBD:: ODBC is unlike most other DBDs in that it connects to literally dozens of possible ODBC Drivers.The only performance penalty is during execute(), but I didn't want to incur that penalty for all circumstances. This attribute will be automatically set when multiple result sets are triggered.Most people shouldn't have to worry about this. This causes a spin-loop (with a small "sleep") until the ODBC API being called is complete (i.e., while the ODBC API returns ).This attribute requires DBI version 1.55 or better. Example: method with a SQL type this overrides everything else above.Use this if you have special needs (such as Oracle triggers, etc) where :new or :name mean something special and are not just place holder names. This is to handle special cases, especially when using multiple result sets.