Rik Smale

> @WikiRik Hope you are doing well. Request your help to review the updated code provided by @hjamil-24 and provide your approval for the same. Thanks for your message @sharadraju...

I believe we've done some work on this in the v7 alphas. Can you check with installing `@sequelize/core@alpha`?

Can you also update the [associated unit tests](https://github.com/sequelize/sequelize/blob/main/packages/core/test/unit/query-interface/upsert.test.ts)? You do do something similar to this; https://github.com/sequelize/sequelize/blob/main/packages/core/test/unit/query-generator/create-schema-query.test.ts to check for a notSupportedError

I'm not sure how well sequelize works on the current version of Deno (we're tracking that here; https://github.com/sequelize/sequelize/issues/12836) or Bun (bun sqlite issue here; https://github.com/sequelize/sequelize/issues/16468). Also JSR is still in...

At this moment none of the maintainers are working on Firebird support and won't be in the forseeable future since there are many other features that we want to add....

Did you try it with the [latest v7 alpha](https://www.npmjs.com/package/@sequelize/core) (alpha-45 at the time of writing)? We've done some work on foreign keys and I think we've fixed this issue

Can you install `@sequelize/core` 7.0.0-alpha.41? It's not published under the `latest` tag but the `alpha` tag. You need to install the same version for `@sequelize/mssql` as well

Feel free to open a PR, I don't think we have encountered this before so no plans to fix it on our side.

CI issue with MSSQL is not due to your change, I'll merge this later

Yes, agree about having it an opt-in option. No need to change defaults and introduce a breaking change