EF Code First: FLOAT Columns generate [Column(TypeName = "float")], which give errors

Question

When I create a simple table with a FLOAT(126) column and add an ADO.NET Entity Data Model with Code first from the database I get a decimal for the FLOAT column with the following ColumnAttribute: [Column(TypeName = "float")].
When I try to add a controller for this generated Code First class, it fails with the following message:
Error:
There was an error running the selected code generator:
'Unable to retrieve metadata for 'MyNamespace.TEMP_WITHFLOAT'.
Schema specified is not valid. Errors:
(8,12) : error 2019: Member Mapping specified is not valid. The type 'Edm.Decimal[Nullable=False,DefaultValie=,Precision=38,Scale=0]' of member 'FLOATCOL' in type 'MyNamespace.TEMP_WITHFLOAT' is not compatible with 'SqlServer.float[Nullable=False,DefaultValue=]' of member 'FLOATCOL' in type 'MySchema.TEMP_WITHFLOAT'.'
It fails with the same error if I specify other values for precision and scale (or remove the lines entirely) in the code invoking HasPrecision in the generated model.
The error message when trying to add a controller for the generated class:
But - if I remove the attribute [Column(TypeName = "float")] from the generated Code First class, the controller is created without errors, and works as it should, returning decimal numbers correctly (it happily ignores that the scale is set to 0 in the generated model).
The generated class with the ColumnAttribute removed:
    [Table("MYDBSCHEMA.TEMP_WITHFLOAT")]
    public partial class TEMP_WITHFLOAT
        [DatabaseGenerated(DatabaseGeneratedOption.None)]
        public int ID { get; set; }
        //[Column(TypeName = "float")]
        public decimal FLOATCOL { get; set; }
Correct JSON output from working controller:
[ { "ID": 1, "FLOATCOL": 123.0 }, { "ID": 2, "FLOATCOL": 123.456789012345 } ]
It would be very nice if the Code First generated classes worked out of the box, without a required step to manually remove the Column attribute for every FLOAT column.
Is there a workaround or other solution to this problem? The best solution would be if the generated code is mapped correctly between compatible database and C# types.
Simple code to reproduce the issue:
SQL script for the table:
CREATE TABLE "TEMP_WITHFLOAT"
   ( "ID" NUMBER(10,0) NOT NULL ENABLE,
  "FLOATCOL" FLOAT(126) NOT NULL ENABLE
   ) PCTFREE 10 INITRANS 1 NOCOMPRESS LOGGING;
ALTER TABLE "TEMP_WITHFLOAT" ADD CONSTRAINT "PK_TEMP_WITHFLOAT" PRIMARY KEY ("ID") ENABLE;
The generated class:
   [Table("MYDBSCHEMA.TEMP_WITHFLOAT")]
    public partial class TEMP_WITHFLOAT
        [DatabaseGenerated(DatabaseGeneratedOption.None)]
        public int ID { get; set; }
        [Column(TypeName = "float")]
        public decimal FLOATCOL { get; set; }
The generated model:
    public partial class TempWithFloatModel : DbContext
        public TempWithFloatModel()
            : base("name=TempWithFloatModel")
        public virtual DbSet<TEMP_WITHFLOAT> TEMP_WITHFLOAT { get; set; }
        protected override void OnModelCreating(DbModelBuilder modelBuilder)
            modelBuilder.Entity<TEMP_WITHFLOAT>()
                .Property(e => e.FLOATCOL)
                .HasPrecision(38, 0);

Answer 1

The annotation is emitted by the entity designer because it is necessary to preserve type fidelity with the source database column.
If the annotation is removed, the FLOATCOL property in the generated class would map to an Oracle number(38) column. But, of course, that is not what the source column is in this case.
For example, this would be a problem if a database initializer was subsequently used to re-create the database or if a script was generated via migrations using the class without the annotation.
It's interesting that the error message refers to SqlServer.float type.
I'll try to investigate a bit more...