Skip to content

Explore adding a timeout parameter for long running table queries #25

@aaroncox

Description

@aaroncox

Currently you can call table.all() and it might take an exceptionally long time, with a very big table.

Do we potentially want a timeout value which it cannot exceed, or potentially to bring cancelable promises over so the developer can abort on their own timeline?

Unsure on priority of this, but recording the idea here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Icebox

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions