mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-17 12:31:52 +03:00
f967a4b22e
Fixes https://github.com/hasura/graphql-engine/issues/6385 In the v1.3.4-beta.2 version, the SQL generated for a query action containing relationship and configured with permissions parsed the `x-hasura-user-id` session variable value through the `hasura.user` postgres setting instead of passing the session variables as an JSON object to the query as it was in v1.3.3. This PR fixes the SQL generation to that of v1.3.3 Co-authored-by: Rakesh Emmadi <12475069+rakeshkky@users.noreply.github.com> GitOrigin-RevId: 838ba812f89b51df7fcead81b9d3c2885dfa39b4 |
||
|---|---|---|
| .. | ||
| remote_joins | ||
| create_user_fail.yaml | ||
| create_user_success.yaml | ||
| create_users_fail.yaml | ||
| create_users_success.yaml | ||
| expecting_array_response.yaml | ||
| expecting_object_response.yaml | ||
| get_user_by_email_fail.yaml | ||
| get_user_by_email_success.yaml | ||
| get_users_by_email_success.yaml | ||
| invalid_webhook_response.yaml | ||
| mirror_action_no_field.yaml | ||
| mirror_action_not_null.yaml | ||
| mirror_action_success.yaml | ||
| mirror_action_unexpected_field.yaml | ||
| query_action_relationship_with_permission.yaml | ||
| schema_setup.yaml | ||
| schema_teardown.yaml | ||
| values_teardown.yaml | ||