Rhett Thompson
Rhett Thompson
This is still an issue for me in Sequelize v6.3.5 with MSSQL. I guess the devs hate us... 🤣 I wonder if this will ever get fixed...
I am having the same issue. I think this is a bug and should be fixed, not have a workaround added to the doc. I believe the core of this...
Further, I believe these other issues are related because _whatever_ dialect does not fully support `sequelize.options.timezone` specifically inside of `sequelize/src/dialects/{SOME_DIALECT}/data-types.js` in the `DATE` & `DATEONLY` parse functions: - #8708 -...
To be clear, the only reason this is an issue with MSSQL specifically, is because `DATEONLY.parse()` uses: ```js class DATEONLY extends BaseTypes.DATEONLY { static parse(value) { return moment(value).format('YYYY-MM-DD'); } }...