Skip to content

improve deleteQuery behaviour around limit #8522

@sushantdhiman

Description

@sushantdhiman

Follow up of discussion in #8494

All dialects implement deleteQuery in such a way that if limit is not supplied only first row is deleted. I am sure this is not a desired behavior and remnant of some old logic that was then copied over to other dialects.

Till now this check is defaulting limit value to null so this current or past versions arent affected.

But I think we need to improve this logic in upcoming sequelize versions

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: refactorDEPRECATED: replace with the "meta" issue type

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions