这是indexloc提供的服务,不要输入任何密码
Skip to content

"Relationship could not be deleted!" #9713

@Californian

Description

@Californian

Version Information

Server Version: v2.27.0-cloud.1

Environment

Cloud
Env vars: HASURA_GRAPHQL_EXPERIMENTAL_FEATURES = naming_convention, graphql format is turned on.

What is the current behaviour?

Dropping an array relationship fails with the following message:

Relationship could not be deleted!
Error when parsing command drop_relationship.
See our documentation at https://hasura.io/docs/latest/graphql/core/api-reference/metadata-api/index.html#metadata-apis.
Internal error message: key "table" not found

What is the expected behaviour?

Dropping relationships succeed.

How to reproduce the issue?

  1. Create a project.
  2. Create three tables, two with uuid ID primary keys (tables "A" and "B"), one with a compound primary key that references the other two (table "C").
  3. Add an array relationship on "A" to "C".
  4. Attempt to drop the above relationship.

Screenshots or Screencast

Screenshot from 2023-06-15 13-34-10

Please provide any traces or logs that could help here.

400 response from /metadata:

{
    "code": "parse-failed",
    "error": "Error when parsing command drop_relationship.\nSee our documentation at https://hasura.io/docs/latest/graphql/core/api-reference/metadata-api/index.html#metadata-apis.\nInternal error message: key \"table\" not found",
    "path": "$.args"
}

Any possible solutions/workarounds you're aware of?

No.

Keywords

Drop relationship, Internal error message: key "table" not found

Metadata

Metadata

Assignees

No one assigned

    Labels

    c/consoleRelated to consolek/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions