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

Permission metadata name cropped after 63 characters #3444

@pnappa

Description

@pnappa

Hi,

I'm currently writing custom migrations, and am generating permissions combinatorially to populate Hasura as manually doing them would take too long.

A problem I hit is this error:

FATA[0006] apply failed: [unexpected] postgres query error ($.args[184].args)
File: '1575004447175_generate_permissions/up.yaml'
{
    "permission": {
        "check": {},
        "columns": "*"
    },
    "role": "supermanadmin.researcheradmin.user.useradmin",
    "table": {
        "name": "QuestionnaireQuestionOnQuestionnaireSubscale",
        "schema": "public"
    }
}
[42P07] FatalError: relation "supermanadmin.researcheradmin.user.useradmin__insert__public__Q" already exists 

This appears to fail because it sees that another permission exists (although it's a different table - I have many tables starting with Q, it just happens to crop off at the same position).

I have a work-around which is, don't make the names of the tables and/or permissions that long, but it would be nice not to hit this in the future.

Cheers,
Patrick

Metadata

Metadata

Assignees

Labels

c/serverRelated to servere/easycan be wrapped up in a couple of daysk/bugSomething isn't workingp/highcandidate for being included in the upcoming sprints/wipStatus: This issue is a work in progress

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions