mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-16 01:44:03 +03:00
6e8da71ece
(Work here originally done by awjchen, rebased and fixed up for merge by jberryman) This is part of a merge train towards GHC 9.2 compatibility. The main issue is the use of the new abstract `KeyMap` in 2.0. See: https://hackage.haskell.org/package/aeson-2.0.3.0/changelog Alex's original work is here: #4305 BEHAVIOR CHANGE NOTE: This change causes a different arbitrary ordering of serialized Json, for example during metadata export. CLI users care about this in particular, and so we need to call it out as a _behavior change_ as we did in v2.5.0. The good news though is that after this change ordering should be more stable (alphabetical key order). See: https://hasurahq.slack.com/archives/C01M20G1YRW/p1654012632634389 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4611 Co-authored-by: awjchen <13142944+awjchen@users.noreply.github.com> GitOrigin-RevId: 700265162c782739b2bb88300ee3cda3819b2e87
23 lines
1.3 KiB
YAML
23 lines
1.3 KiB
YAML
description: The explained MSSQL subscription in our documentation
|
|
url: /v1/graphql/explain
|
|
status: 200
|
|
response:
|
|
sql: "SELECT [row].[result_id] AS [result_id],\n [result].[json] AS [result]\n\
|
|
FROM OPENJSON((N''+NCHAR(91)+''+NCHAR(91)+''+NCHAR(34)+'00000000-0000-0000-0000-000000000000'+NCHAR(34)+','+NCHAR(123)+''+NCHAR(34)+'cursor'+NCHAR(34)+''+NCHAR(58)+''+NCHAR(123)+''+NCHAR(125)+','+NCHAR(34)+'query'+NCHAR(34)+''+NCHAR(58)+''+NCHAR(123)+''+NCHAR(125)+','+NCHAR(34)+'session'+NCHAR(34)+''+NCHAR(58)+''+NCHAR(123)+''+NCHAR(125)+','+NCHAR(34)+'synthetic'+NCHAR(34)+''+NCHAR(58)+''+NCHAR(91)+''+NCHAR(93)+''+NCHAR(125)+''+NCHAR(93)+''+NCHAR(93)+''))\n\
|
|
\ WITH ([result_id] uniqueidentifier '$[0]',\n [result_vars] NVARCHAR(MAX)\
|
|
\ '$[1]' AS JSON) AS [row]\nOUTER APPLY (SELECT (SELECT ISNULL((SELECT [t_user1].[name]\
|
|
\ AS [name]\n FROM [dbo].[user] AS [t_user1]\n \
|
|
\ FOR JSON PATH, INCLUDE_NULL_VALUES), (N''+NCHAR(91)+''+NCHAR(93)+''))\
|
|
\ AS [root]) AS [user]\n FOR JSON PATH, INCLUDE_NULL_VALUES, WITHOUT_ARRAY_WRAPPER)\
|
|
\ \nAS [result]([json])\nFOR JSON PATH, INCLUDE_NULL_VALUES"
|
|
|
|
query:
|
|
query:
|
|
query: |
|
|
subscription getUsers {
|
|
user {
|
|
name
|
|
}
|
|
}
|
|
operationName: getUsers
|