The attached patch removes a doubled NUM_PREC_RADIX entry from
the index hash (and adjusts the following indexes).
BTW: These sentences sound somewhat contradicting:
The index values shown above (e.g., NULLABLE => 6) are for
illustration only. Drivers may define the fields with a
different order.
Even though an 'index' hash is provided, all the field names
in the index hash defined above will always have the index
values defined above.
It seems that DBI currently encourages the second statement:
Carp::croak("type_info_all returned non-standard DATA_TYPE index value ...
Steffen*** DBI.orig Sat Aug 23 00:25:40 2003
--- DBI.pm Mon Nov 17 09:56:50 2003
***************
*** 4035,4045 ****
LOCAL_TYPE_NAME => 12,
MINIMUM_SCALE => 13,
MAXIMUM_SCALE => 14,
! NUM_PREC_RADIX => 15,
! SQL_DATA_TYPE => 16,
! SQL_DATETIME_SUB => 17,
! NUM_PREC_RADIX => 18,
! INTERVAL_PRECISION=> 19,
},
[ 'VARCHAR', SQL_VARCHAR,
undef, "'","'", undef,0, 1,1,0,0,0,undef,1,255, undef
--- 4035,4044 ----
LOCAL_TYPE_NAME => 12,
MINIMUM_SCALE => 13,
MAXIMUM_SCALE => 14,
! SQL_DATA_TYPE => 15,
! SQL_DATETIME_SUB => 16,
! NUM_PREC_RADIX => 17,
! INTERVAL_PRECISION=> 18,
},
[ 'VARCHAR', SQL_VARCHAR,
undef, "'","'", undef,0, 1,1,0,0,0,undef,1,255, undef
