I've implemented $dbh->column_info() for DBD::Sybase, using the sp_columns catalog stored procedure that Sybase provides.
However - I noticed a discrepancy between the columns that the DBI manual defines and the columns that sp_columns returns - sp_columns returns two extra columns between REMARKS and COLUMN_DEF, called SS_DATA_TYPE and COLID (where SS_DATA_TYPE is the internal Sybase data type id, and COLID is really the same thing as ORDINAL_POSITION). I don't know which of the definitions is "wrong". As an additional question - how many drivers actually impelement column_info() ? (I just noticed that DBD::mysql doesn't, for example, and I don't know if mysql has an easy way to get that information in a reasonable format). Michael -- Michael Peppler / [EMAIL PROTECTED] / http://www.mbay.net/~mpeppler [EMAIL PROTECTED] / ZetaTools, Inc / http://www.zetatools.com ZetaTools: Call perl functions as Sybase stored procedures!
signature.asc
Description: This is a digitally signed message part
