D6What it costs the developer
Can I just look at my data?
Browse the tables. Run a query. Draw the ERD. Export the schema. All possible, never already there.
What actually goes wrong
Answering “did that actually save” means a database client, credentials for an environment you may not have, and a connection that works from where you are standing.
So the question gets answered with a log line instead, and half of all bug reports are a row that is exactly what the code wrote.
What Grit does about it
- A database browser is mounted at /studio in every project: tables, rows, filters, foreign keys followed, a query runner and an ERD drawn from the schema.
- It is the same tool in development and against a deployed database, so the question is answered the same way everywhere.
The commands
Already running with the API
grit start# http://localhost:8080/studio
Or open it directly
grit studio
What it does not do
Studio sits underneath the ownership scoping. A row you can see there and cannot fetch through the API is usually the scoping working, not a bug.