-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
c/consoleRelated to consoleRelated to consolec/migrationsRelated to migrationsRelated to migrationse/easycan be wrapped up in a couple of dayscan be wrapped up in a couple of daysk/bugSomething isn't workingSomething isn't working
Description
I am pretty sure the console creates suspicious migrations. Here a the reproductible steps:
- Start with a fresh Hasura instance & a fresh database as well;
- Set up a project directory & Open the console from the CLI (as show in the documentation);
- Create a table
testwith atscolumn, selectingTimestampas the type (and notTime,time without time zonenortimestamp without time zone). Usetsas the PK. You shoud see the following migration now:
CREATE TABLE "public"."test"("ts" timestamptz NOT NULL, PRIMARY KEY ("ts") );- Edit the
tscolumn, change itsGraphQL field name& save. Now you will see the following suspicious migrations:
ALTER TABLE "public"."test" ALTER COLUMN "ts" TYPE timestamp with time zone;
ALTER TABLE "public"."test" DROP CONSTRAINT "test_ts_key";Hope this report will lead to a better product!
slimlime
Metadata
Metadata
Assignees
Labels
c/consoleRelated to consoleRelated to consolec/migrationsRelated to migrationsRelated to migrationse/easycan be wrapped up in a couple of dayscan be wrapped up in a couple of daysk/bugSomething isn't workingSomething isn't working