Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

standardise how session variables are passed to postgres #825

Closed
0x777 opened this issue Oct 20, 2018 · 0 comments
Closed

standardise how session variables are passed to postgres #825

0x777 opened this issue Oct 20, 2018 · 0 comments
Assignees
Labels
c/server Related to server p/high candidate for being included in the upcoming sprint

Comments

@0x777
Copy link
Member

0x777 commented Oct 20, 2018

This will help anyone willing to capture this information from Postgres. For example, insert/update/delete triggers for audit trail.

Currently, you can access them with current_setting('hasura.user_id'). For every, x-hasura-param, the x-hasura- is dropped and in rest of the suffix, hyphens are replaced with underscores. Ideally, we can have this to be a json which can simply be captured with current_setting('hasura.session').

@0x777 0x777 added c/server Related to server p/high candidate for being included in the upcoming sprint labels Oct 20, 2018
@0x777 0x777 self-assigned this Oct 20, 2018
@dsandip dsandip added this to the v1.0.0-alpha26 milestone Oct 23, 2018
@0x777 0x777 closed this as completed in ab9692d Oct 24, 2018
rikinsk-zz pushed a commit to rikinsk-zz/graphql-engine that referenced this issue Oct 25, 2018
hasura-bot pushed a commit that referenced this issue Jul 15, 2024
### What
Much like hasura/v3-engine#824, we combine
relay-related errors into `RelayError`.

### How
Remove them from the big `Error` type.

---------

Co-authored-by: Daniel Chambers <daniel@hasura.io>
V3_GIT_ORIGIN_REV_ID: b26460c6aa4d622c6f5548e5cd294c7480acdca4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c/server Related to server p/high candidate for being included in the upcoming sprint
Projects
None yet
Development

No branches or pull requests

2 participants