hasura / hasura/graphql-engine
Document prepared statements behaviour
Open
c/docs
k/bug
p/medium
s/docs-is-actioned
t/native-dbs
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Document prepared statements optimisation/cost. Some information available in a [blog post](https://hasura.io/blog/fast-graphql-execution-with-query-caching-prepared-statements/). More information on cost of using this feature is also needed.
Contributor guide
Research direction
No file, test, or documentation entry point is identified in the issue. Start by reviewing the linked blog post and the repository's existing documentation for prepared statements; the work is done when the optimization behavior and its usage cost are documented with enough detail for users to understand the tradeoffs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100