Open PedroBern opened 3 years ago
Server Version: v2.0.9-cloud.
Cloud
Update schema after migrations
Custom field, schema, introspection
last migration is:
-- down ALTER TABLE "public"."wod" ALTER COLUMN "name" TYPE citext; -- up ALTER TABLE "public"."wod" ALTER COLUMN "name" TYPE varchar(128);
The schema should be String, but it continues to be citext see the screen shot below.
String
citext
It happens for 2 of my tables.
Tried reloading metadata, but didn't work.
👆
Update: after 1 day, the next deployment of the cloud fixed the issue >>>> breaking the client that was using the previous schema. In this case was a simple fix, just 2 fields, but this continues to be a cloud bug.
Version Information
Server Version: v2.0.9-cloud.
Environment
Cloud
What is the expected behaviour?
Update schema after migrations
Keywords
Custom field, schema, introspection
What is the current behaviour?
last migration is:
The schema should be
String
, but it continues to becitext
see the screen shot below.It happens for 2 of my tables.
Screenshots or Screencast
Possible solution
Tried reloading metadata, but didn't work.
Works locally, but not on Cloud
👆