Why would you want to use that info?
Well, I was hoping I wouldn't have to create a different type converter for every variation of the numeric data type in our database. After querying the system tables in our database I found that there are 17 distinct variations of the numeric data type (meaning different lengths, precision and scale). Some of these variations map to different .NET data types, depending on the precision and scale.
I'm going to play with using a single type converter (using the SDK code) and then use the designer to add new type conversion definitions. Maybe each type conversion definition can use the same type converter, but each can apply it's own filter based on the native data type, precision, scale, etc.
Thanks again for adding the type converter feature!