mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-15 01:12:56 +03:00
docs: miscellaneous fixes
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7503 GitOrigin-RevId: 9eebf9f1d10ca7a94bfb42770bc35c68add98817
This commit is contained in:
Rikin Kachhia
hasura-bot
parent
af639392ce
commit
7275b6e39a
@ -933,18 +933,6 @@ When you track a table in Hasura, by default it exposes all the root fields avai
|
||||
you may want a role to only have access to certain root fields of a table or have the table be accessible only through
|
||||
[relationships](/schema/postgres/table-relationships/index.mdx).
|
||||
|
||||
:::info Note
|
||||
|
||||
Only query and subscription root fields can be disabled.
|
||||
|
||||
:::
|
||||
|
||||
:::tip Supported from
|
||||
|
||||
Disabling root fields is supported in version `v2.8.0` and above.
|
||||
|
||||
:::
|
||||
|
||||
<Tabs groupId="user-preference" className="api-tabs">
|
||||
|
||||
<TabItem value="console" label="Console">
|
||||
@ -1035,6 +1023,18 @@ all fields are allowed and an empty array means no fields are allowed.
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
|
||||
:::info Note
|
||||
|
||||
Only query and subscription root fields can be disabled.
|
||||
|
||||
:::
|
||||
|
||||
:::tip Supported from
|
||||
|
||||
Disabling root fields is supported in version `v2.8.0` and above.
|
||||
|
||||
:::
|
||||
|
||||
#### Use cases
|
||||
|
||||
##### 1. Allow a table to be accessible only through a relationship
|
||||
|
||||
@ -35,13 +35,11 @@ Here are 2 ways you can get started with Hasura and SQL Server:
|
||||
|
||||
## Supported features
|
||||
|
||||
Hasura currently supports queries, subscriptions, mutations, relationships and permissions on MS SQL Server.
|
||||
Hasura currently supports queries, subscriptions, mutations, relationships, permissions, and Event Triggers on MS SQL Server.
|
||||
|
||||
Next up on our roadmap for Hasura + SQL Server:
|
||||
|
||||
- Support for stored procedures & custom functions ([#7073](https://github.com/hasura/graphql-engine/issues/7073))
|
||||
- Event Triggers: Trigger HTTP webhooks with atomic capture and atleast once guarantee whenever data changes inside the
|
||||
database ([#7075](https://github.com/hasura/graphql-engine/issues/7075))
|
||||
- Remote Joins: Join models in SQL Server to models from other API services (GraphQL or REST)
|
||||
([#7076](https://github.com/hasura/graphql-engine/issues/7076))
|
||||
|
||||
|
||||
@ -37,12 +37,14 @@ the `type` field in a log line, which indicates which sub-system the log comes f
|
||||
For example, the HTTP webserver logs incoming requests as an access log and is called `http-log`. Similarly logs from
|
||||
the websocket layer are called `websocket-log`, logs from the Event Trigger system are called `event-trigger` etc.
|
||||
|
||||
You can configure the GraphQL Engine to enable/disable certain log-types using the the `--enabled-log-types` flag or the
|
||||
You can configure the GraphQL Engine to enable/disable certain log-types using the `--enabled-log-types` flag or the
|
||||
`HASURA_GRAPHQL_ENABLED_LOG_TYPES` env var. See
|
||||
[GraphQL Engine server config reference](/deployment/graphql-engine-flags/reference.mdx)
|
||||
|
||||
Default enabled log-types are: `startup, http-log, webhook-log, websocket-log, jwk-refresh-log`
|
||||
|
||||
### Configurable log-types
|
||||
|
||||
All the log-types that can be enabled/disabled are:
|
||||
|
||||
| Log type | Description | Log Level |
|
||||
@ -54,7 +56,8 @@ All the log-types that can be enabled/disabled are:
|
||||
| `webhook-log` | Logs responses and errors from the authorization webhook (if setup) | `info` and `error` |
|
||||
| `jwk-refresh-log` | Logs information and errors about periodic refreshing of JWK | `info` and `error` |
|
||||
|
||||
Configurable log-types
|
||||
|
||||
### Internal log-types
|
||||
|
||||
Apart from the above, there are other internal log-types which cannot be configured:
|
||||
|
||||
@ -68,7 +71,6 @@ Apart from the above, there are other internal log-types which cannot be configu
|
||||
| `schema-sync-thread` | Logs internal events, when it detects schema has changed on Postgres and when it reloads the schema | `info` and `error` |
|
||||
| `health-check-log` | Logs source Health Check events which includes health status of a data source | `info` and `warn` |
|
||||
|
||||
Internal log-types
|
||||
|
||||
## Logging levels
|
||||
|
||||
|
||||
@ -43,12 +43,6 @@ Partial unique indexes cannot be used in the `constraint` field.
|
||||
|
||||
:::
|
||||
|
||||
:::info Note
|
||||
|
||||
Partial unique indexes cannot be used in the `constraint` field.
|
||||
|
||||
:::
|
||||
|
||||
:::info Fetching Postgres constraint names
|
||||
|
||||
You can fetch details of unique or primary key constraints on a table by running the following SQL:
|
||||
|
||||
@ -38,11 +38,11 @@ Choose a pricing plan and select a region for your project.
|
||||
|
||||
Once you have completed the project setup, click `Create Project`.
|
||||
|
||||
## Step 2: Database setup {#cloud-projects-db-setup}
|
||||
|
||||
Once created, you can specify a new name for your Project if you want.
|
||||
|
||||
Then to get started, Click `Launch Console` to open the Hasura Console in your browser.
|
||||
## Step 2: Database setup {#cloud-projects-db-setup}
|
||||
|
||||
Click `Launch Console` to open the Hasura console in your browser.
|
||||
|
||||
<Thumbnail
|
||||
src="/img/projects/create-project-assign-name_console_2.12.png"
|
||||
|
||||
Loading…
Reference in New Issue
Block a user