Remove column mapping to JDBC type FLOAT for SQL Server

[nscuro]

The JDBC driver does not provide this type. According to https://learn.microsoft.com/en-us/sql/connect/jdbc/using-basic-data-types?view=sql-server-ver16, the SQL type FLOAT is mapped to the JDBC type DOUBLE.

dbinfo output of the schema tool is provided for the last three major versions of the JDBC driver.

This addressed #304

[andyjefferson]

Thx for the PR. No real issue with this fix, but why not go one step further ... add support for JDBC FLOAT if it isn't provided by the JDBC Driver. You do this by adding an entry for Types.FLOAT in the initialiseTypes method, map it to sqlType of "float", and then you can have entries for the different Java types to allow people to specify it as JDBC type = float

[nscuro]

Sure, I can give that a go.

I see there is already an "artificial" mapping for DOUBLE:

datanucleus-rdbms/src/main/java/org/datanucleus/store/rdbms/adapter/SQLServerAdapter.java

Lines 177 to 179 in fcc9722

	sqlType = new org.datanucleus.store.rdbms.adapter.SQLServerTypeInfo(
	"float", (short)Types.DOUBLE, 53, null, null, null, 1, false, (short)2, false, false, false, null, (short)0, (short)0, 2);
	addSQLTypeForJDBCType(handler, mconn, (short)Types.DOUBLE, sqlType, true);

It seems like the mapping would be identical for FLOAT, so just adding

addSQLTypeForJDBCType(handler, mconn, (short)Types.FLOAT, sqlType, true);

below the above snippet should do the trick?

[nscuro]

Thanks for merging @andyjefferson!

Do you have a rough idea of when 6.0.2 will be released? :) I'm eagerly waiting for #449 to be shipped, as the corresponding bug prevents our users with SQL server from running our project.

[andyjefferson]

Since only datanucleus-core and datanucleus-rdbms to release (so a plugin release, rather than accessplatform), maybe some time in the next week