On Mon, Jun 10, 2002 at 01:10:51PM -0400, Pradeep Padala wrote: > > And I'd like to drum home the point that *all* driver authors should > > be adding support for get_info(). It's not hard, especially if there's > > an ODBC driver available for the same database. > > I have one question regarding this. Should I hardcode the numbers in the > driver?
Only hardcode things that can't change. Everything else should be got from the server via API calls or SQL etc (or maybe picked from a set of hardcoded alternatives based on the server version number). > The DBI spec says that it hasn't defined SQL_DBMS_VER etc.. When > will it be included? I'm not sure what you mean by "hasn't defined SQL_DBMS_VER". The DBI spec says "doesn't provide a name to number mapping for the information type codes or the results. Applications are expected to use the integer values directly". There is a DBI::Const::GetInfo module that defines the constants but the interface to that is changing. Anyway, it's *not needed* as the corresponding numbers are fixed: SQL_DBMS_VER == 18. > For now, what's the best way to handle this for drivers other than ODBC? Handle what? Tim.
