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

Using suggested relationships via console on foreign keys on tables across postgres schemas causes bug #876

@david-studyblue

Description

@david-studyblue

If I track tables in the PUBLIC schema, and then track the suggested relationships, all via the console, then Hasura seems to work properly. If I track tables in another schema, and then track the suggested relationships for those tables, Hasura gets into a weird state. Specifically, the suggested relationship isn't removed from the UI component displaying the suggested relationships, though it seems like the relationship nevertheless is tracked. Or something. I'll try to illustrate it with SQL and with screenshots.

I'll paste in the SQL that I used to set up the test, and then I'll attach some screenshots that illustrate the problem.

-- -*- sql-product: postgres; -*-

-- Create related tables in the public schema

create table parent (
id serial primary key);

create table child (
id serial primary key,
creator_id int not null references parent (id));

-- Create related tables in the test schema

create schema test;

create table test.parent (
id serial primary key);

create table test.child (
id serial primary key,
creator_id int not null references test.parent (id));

screenshot from 2018-10-26 16-25-12
screenshot from 2018-10-26 16-25-21
screenshot from 2018-10-26 16-25-29

Metadata

Metadata

Assignees

No one assigned

    Labels

    c/consoleRelated to consolep/urgentImmediate action required

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions