sequelize: MSSQL 2016 DATETIME field updates broken due to DATETIME2 use

I’ve got an MSSQL db, with DATETIME fields (not DATETIMEOFFSET) and no matter what I do with sequelize/models, I can’t get updates to work without a casting error. If I update my DB to DATETIMEOFFSET (which I tested thanks to other similar issues I found), all is well. I think the presumed DATETIMEOFFSET use (from DATE) is too aggressive and I need to undo it rather than get pushed into a schema change. There an option/flag that will accomplish that, or is this a bug?

What are you doing?

Model definition for Batch

module.exports = function(sequelize, DataTypes) {
  return sequelize.define('Batch', {
    ID: {
      type: DataTypes.INTEGER,
      allowNull: false,
      primaryKey: true,
      autoIncrement: true
    },
    BatchDate: {
      type: DataTypes.DATE,
      allowNull: true,
      defaultValue: '(getdate())'
    },
  {
    tableName: 'Batch',
    timestamps: false,
    paranoid: true,
    freezeTableName: true,
    hasTrigger: true
  });
};

#Try to update Batch.BatchDate with a perfectly valid date

Batch.find( { where: { ID: 31243 } } )
.then( batch => {
    batch.BatchDate = new Date("2028-01-01T00:00:00.000Z");
    batch.save();

    //// The Following throws the exact same error as the use of save() above
    //
    // batch.update(
    //     { BatchDate: "2038-01-01T00:00:00.000Z" },
    //     { where: { ID: 31243 } } )
    //     .then( res => {
    //         app.bm.mods.sequelize.models.Batch.findAll( { where: { id: 31243 } } )
    //         .then( res => {
    //             console.dir( res );
    //         });
    //     })
    //     .catch( err => {
    //         console.dir ( err );
    //     });

});

#NOTE the ‘DATETIMEOFFSET’ use rather than DATETIME

exec sp_executesql @statement=N'declare @tmp table ([ID] INTEGER,[BatchDate] DATETIMEOFFSET);UPDATE [Batch] SET [BatchDate]=N''2028-01-01 00:00:00.000 +00:00'' OUTPUT INSERTED.[ID],INSERTED.[BatchDate] into @tmp WHERE [ID] = 31243;select * from @tmp'

What do you expect to happen?

I expected Sequelize to run an UPDATE transaction, setting the value of BatchDate as a standard JS Date and SQL DATETIME (not DATETIMEOFFSET).

What is actually happening?

SequelizeDatabaseError: Conversion failed when converting date and/or time from character string.

Sequelize is using DATETIMEOFFSET instead of the defined DATETIME.

Dialect: mssql Dialect version: 2016 Database version: 2016 Sequelize version: 4.2.x and 4.37.6 Tested with latest release: Yes, 4.37.6