Skip to content

resort should be False by default #3

@AndrewVSutherland

Description

@AndrewVSutherland

I realize that resorting is disabled but it would make developer's lives a lot easier if resort=False by default in the update, delete, and insert_many methods (particularly update).

Otherwise you have to remember to explicitly disable resort in every call to prevent the console from being overwhelmed by "resorting disabled" messages when you debugging.

I see no downside to making this change (certainly no one has written any code that assumes resorting will automatically happen when they make an update, since this has never been done).

I would also argue that if and when you ever do decide to enable resorting, you still don't want it to happen by default, it will be too expense.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions