graphql-engine/server/tests-py/queries/v2/mssql/run_sql/setup_mssql.yaml

type: bulk
args:

# track tables
- type: mssql_track_table
  args:
    source: mssql
    table:
      name: author

- type: mssql_track_table
  args:
    source: mssql
    table:
      name: article

# create relationships
- type: mssql_create_object_relationship
  args:
    source: mssql
    table: article
    name: author
    using:
      foreign_key_constraint_on: author_id

- type: mssql_create_array_relationship
  args:
    source: mssql
    table: author
    name: articles
    using:
      foreign_key_constraint_on:
        table: article
        column: author_id
server/mssql: add cascade to mssql_run_sql <!-- Thank you for ss in the Title above ^ --> ## Description <!-- Please fill thier. --> <!-- Describe the changes from a user's perspective --> We don't have dependency reporting mechanism for `mssql_run_sql` API i.e when a database object (table, column etc.) is dropped through the API we should raise an exception if any dependencies (relationships, permissions etc.) with the database object exists in the metadata. This PR addresses the above mentioned problem by -> Integrating transaction to the API to rollback the SQL query execution if dependencies exists and exception is thrown -> Accepting `cascade` optional field in the API payload to drop the dependencies, if any -> Accepting `check_metadata_consistency` optional field to bypass (if value set to `false`) the dependency check ### Related Issues <!-- Please make surt title --> <!-- Add the issue number below (e.g. #234) --> Close #1853 ### Solution and Design <!-- How is this iss --> <!-- It's better if we elaborate --> The design/solution follows the `run_sql` API implementation for Postgres backend. ### Steps to test and verify <!-- If this is a fehis is a bug-fix, how do we verify the fix? --> - Create author - article tables and track them - Defined object and array relationships - Try to drop the article table without cascade or cascade set to `false` - The server should raise the relationship dependency exists exception ## Changelog - ✅ `CHANGELOG.md` is updated with user-facing content relevant to this PR. If no changelog is required, then add the `no-changelog-required` label. ## Affected components <!-- Remove non-affected components from the list --> - ✅ Server - ❎ Console - ❎ CLI - ❎ Docs - ❎ Community Content - ❎ Build System - ✅ Tests - ❎ Other (list it) PR-URL: https://github.com/hasura/graphql-engine-mono/pull/2636 GitOrigin-RevId: 0ab152295394056c4ca6f02923142a1658ad25dc 2021-10-22 17:49:15 +03:00			`type: bulk`
			`args:`

			`# track tables`
			`- type: mssql_track_table`
			`args:`
			`source: mssql`
			`table:`
			`name: author`

			`- type: mssql_track_table`
			`args:`
			`source: mssql`
			`table:`
			`name: article`

			`# create relationships`
			`- type: mssql_create_object_relationship`
			`args:`
			`source: mssql`
			`table: article`
			`name: author`
			`using:`
			`foreign_key_constraint_on: author_id`

			`- type: mssql_create_array_relationship`
			`args:`
			`source: mssql`
			`table: author`
			`name: articles`
			`using:`
			`foreign_key_constraint_on:`
			`table: article`
			`column: author_id`