Skip to content

Catching run-away queries #1005

@justinclift

Description

@justinclift

In email conversation with @h4yn0nnym0u5e, one somewhat frustrating thing that can crop up when using DB4S (manually, in the "Execute SQL" tab) is getting a join wrong, and the result set tries to return a huge number of rows. eg 1.6 mill rows

@MKleusberg @innermous @prutz1311 Any idea if there is some way we could catch that kind of thing - without needing a large amount of code change - and not let it go out of control?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions