JDBC types in metadata for FLOAT and INT UNSIGNED are different than in ConnectorJ

The getColumnType() method of java.sql.ResultSetMetaData returns an
SQL type code (one of the constants in java.sql.Types). For some MySQL
types, the implementation of this method in the MariaDB Java Client
returns a different code than the implementation in MySQL
Connector/J. For example, for a column declared as "INT UNSIGNED", the
MariaDB Java Client returns BIGINT, but MySQL Connector/J returns
INTEGER.

This gives problems with Hibernate, which uses this metadata to do its
thing.

Here is the list of numerical types for which I found a mismatch:

(INT and INTEGER are equivalent of course)

I'm attaching two patches:

• The first one to make the current trunk compile (which it doesn't,
  at least not for me, because of a '-' in a method name).
• The second fixes the problem, fixes the unit tests and adds one more
  unit tests, that combines test the metadata with actual data as
  well.