hyper63 / hyper63/hyper

Data Index EXPLAIN plan

Open
#487 0 comments 0 reactions 0 assignees View on GitHub
data index
Dominant language
TypeScript
Stars
79
Forks
12
PR merge metrics
No merged PRs in 30d

Description

## Use Case

> As a developer building on top of the hyper cloud and trying to debug performance issues with our indexes
> I want to utilize an `EXPLAIN` endpoint within the data API
> so that I can make sure that the indexes we expect are being used are actually being used.

## Notes

Requested by Travis Nesland.

Tom: I think a explain feature is a valid request and I believe many databases support an explain feature, I think we would need to be able to support a not implemented response as well for adapter implementers

Tyler: I agree with that. There are cases where an adapter might not implement an explain ie. sqlite adapter or something to that effect. Seems like the sort of thing that would be documented as a convention, then maybe a pre-canned util for adapter devs to use ie. NotImplementedHyperErr() or something.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.