Track all "id_unique" in the GraphQL schema because it is not a valid

[HT-Moh]

I restored the database using Prisma, and once I go to Hasura and click Track all got the following error

cannot include "accounts.compound_id_unique" in the GraphQL schema because it is not a valid GraphQL identifier.

The workaround which far from ideal. I removed all unique from the schema, push the schema once again and then track all, and once again I need to put unique back.

Is there any solution for this problem?

Hasura: v2.0.9

[some-user123]

Regarding the workaround: Do I have to DROP and CREATE constraints for each database? I won't be able to do that on production...

Is there an ETA for a fix?

(I don't even want to track all, but I want to track a table that has a unique constraint. Which does not seem like very unusual use case to me...)

[BenoitRanque]

Is this a duplicate of #7850?

[BenoitRanque]

@some-user123 you do not need to drop and create the constraint, instead you can rename them like this:

ALTER TABLE "schema_name"."table_name" RENAME CONSTRAINT "constraint_name" TO "new_constraint_name";

[jflambert]

I have the same problem but with a - inside of an index name (hasura 2.13.0)

I am unable to rename the offending constraint because it's not my database