hasura / hasura/graphql-engine

[console] Add a read-only flag to run_sql

Open
#7,661 0 comments 0 reactions 0 assignees View on GitHub
c/console estimate/L k/enhancement p/medium
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

While working with a read-only database, using run_sql is not possible because the default transaction mode is read-write and isn't read-only. I can work around this by manually setting the "read_ony" flag to true in the API call.

Given that Hasura now works with read-only databases, making Hasura console work well with read only databases could be an overall umbrella issue that we start tracking as well!

Contributor guide

Open the contributing guide

Research direction

Start at the Hasura console's run_sql entry point and trace the API request it sends, using the issue's read-only database scenario as the first case to reproduce. Done means the console can pass a read-only setting for run_sql and the request works against a read-only database.

Written by the indexing model from the issue text.

Assessment

Domain
databases, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.