[libdbi-devel] DBI_TYPE_STRING has overloaded meaning

[Jan E. <je...@in...>]

It is currently impossible to distinguish an SQL column of decimal(m,n) 
type from an SQL column of string type within libdbi, because both get 
mapped to DBI_TYPE_STRING.
I feel inclined to break this up such that SQL DECIMAL gets mapped to 
DBI_TYPE_DECIMAL, and SQL FLOAT/DOUBLE get mapped to a new 
DBI_TYPE_FLOAT. Or other names. In any case, it will require changes to 
applications in any case, so that's the impact.