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.

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
libdbi-devel mailing list
libdbi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libdbi-devel

Reply via email to