Logging Warnings/Errors and Debugging info
@olirice is already working on this.
Since Jul 31, 2023.
Assessment
This issue has not been assessed yet.
Description
GraphQL queries are typically passed as arguments to a prepared statement and are not logged. Transpired SQL queries executed via SPI are similarly unlogged. That makes it difficult for users to debug their own queries
This issue is to add debug level logging for:
- GraphQL query
- Transpiled SQL queries
- The user's role and uid
with a trace_id
We should also add logging at the warning or error level for things like like naming collisions
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 141
- Avg merge
- 19m
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/pg_graphql
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
supabase/pg_graphql#646 ·
-
triage-required
supabase/pg_graphql#642 · 1 assignee ·
-
triage-required
supabase/pg_graphql#641 · 1 comment · 1 assignee ·
-
triage-required
supabase/pg_graphql#629 · 1 assignee ·
-
triage-required
supabase/pg_graphql#617 · 1 comment · 1 assignee ·
All issues in supabase/pg_graphql
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100