Hi,

I am almost finished a number of changes to DBD::ODBC which a) make it work on win64 platforms and b) reduce the number of ODBC calls required for select statements. I would like to tidy up some of DBD::ODBC which may have fallen behind DBI::DBD changes/improvements but I am having some difficulty deciding what is old/deprecated and what the new "methods" are. Specifically:

o can I now throw away any DBIh_EVENT2 calls as they are now noops?
  e.g. DBIh_EVENT2(drh, ERROR_event, DBIc_ERR(imp_drh),
                   DBIc_ERRSTR(imp_drh));
o in the connect/login method how do I signal a warning?
Specifically, I have changed the code which required two passes through the same metadata calls to work out how much memory was required to store column names to use SQLGetInfo(SQL_MAX_COLUMN_NAME_LEN) but would like to warn if this result used was pinned at what I have decided is a reasonable maximum.

Obviously I've looked at DBI::DBD but it seems more orientated to writing a new DBD than historical changes in DBI internals.

Are there any other changes in DBI::DBD that DBD::ODBC may have fallend behind on I should look for?

Any help would be much appreciated.

Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com

Reply via email to