Alyx

I think this feature would be a really nice addition to the project, but implementing it requires touching parts of the code that are incredibly complicated (the different query generator...

Adding `limit` turns the query into a subQuery to ensure `limit` only impacts how many users are returned. Adding `subQuery: false` could solve your issue, [with a caveat](https://github.com/sequelize/sequelize/blob/main/src/model.d.ts#L792-L819), but this...

We were testing using Issuehunt to implement issue bounties in Sequelize, but it looks like Issuehunt hasn't had much activity in the past year. It's also very instable. I'm rolling...

Nobody from the team is currently working on this. It's a very complex issue. The first step to solving this issue would be to figure out what a correctly generated...

@carsonweinand Your use case is the exact one that would really benefit from supporting this syntax in subQueries. That unfortunately means that right now your only option is to write...

I think I figured out a way to solve this To sum things up: ## The issue When using `limit` and `include` in the same query, the expected behavior is...

I looked into this because it's impacted by PR #14505. The main issue is that `COUNT` returns a bigint in MySQL / pg (probably more), `SUM` returns a decimal. Neither...

`_previousDataValues` is meant to represent the state of the DB, without the currently unsaved changes. `dataValues` is meant to include the unsaved changes. For that reason, `_previousDataValues` & `dataValues` will...

This looks like the same issue as https://github.com/sequelize/sequelize/issues/12971

What would be the difference with `Model.upsert`?