Benoit Ranque
Benoit Ranque
Any chance this gets merged before 2.0 exits the alpha stage?
Users attempting to migrate existing databases to hasura may encounter this issue. Currently the best way around this is to identify and rename all offending constraints. This query can help...
Important note that the workaround above is just that: a workaround. We cannot assume that all users will have the ability to modify their database schema, [case in point](https://github.com/hasura/graphql-engine/issues/7546#issuecomment-1284311875).
Is this a duplicate of #7850?
@some-user123 you do not need to drop and create the constraint, instead you can rename them like this: ```sql ALTER TABLE "schema_name"."table_name" RENAME CONSTRAINT "constraint_name" TO "new_constraint_name"; ```
This would be very useful for my project as well. In my case I need to support Date, Time, DateTime, Timestamp, Interval, Duration PostgreSQL types. I have failed to find...
Realizing now I pushed to the branch I initially created the plugin with. Unsure if this is an issue. Please let me know if there's any action needed on my...
My bad, I missed the conversations here. I have rebased the branch, I think
This commit history is scary, I am not convinced it was supposed to look this way, probably messed something up
> @BenoitRanque if youre still pushing this in I have what I think is a similar issue. > > I am not knowledgable about how it works, but I have...