Do you think that "just" the jdbc type code is enough to determine the SqlTypeDescriptor? I mean users might want use proprietary/dbms-specific types that have the same jdbc type code as other SqlTypeDescriptors.
I also think it might be desirable to allow users to override the type mapping strategy. Would that be possible right now? I'm imagining a contract that has access to the Java member and components(JavaTypeDescriptor etc.) like listed above which based on that information would construct a BasicType or maybe even a UserType? I'm thinking of mapping e.g. some user class to a JSON field.