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

Columns with trim() unique constraints aren't trackable anymore in 2.8 #8601

@Zerebokep

Description

@Zerebokep

Version Information

Server Version: Hasura 2.8
CLI Version (for CLI related issue): Hasura 2.8

Environment

Official Docker image

What is the expected behaviour?

Tracking a table

What is the current behaviour?

Tables which contain a unique index with TRIM() results in an error when trying to track that table.

"error": "Error in $['unique_constraints'][0].columns: parsing [] failed, expected Array, but encountered Null",

How to reproduce the issue?

  1. Create a table with an unique index:

CREATE UNIQUE INDEX test_key ON "users" (trim(first_name))

  1. track that table in hasura

Metadata

Metadata

Assignees

No one assigned

    Labels

    k/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions