fix(graphql-migrations): migration failed for auto increments column

[craicoverflow]

Fixes #2047

Could not add a unit test for this because it is only a Postgres issue - we do need to think about integration tests for this scenario but due to it being a blocker we should get it merged and release first.

[machi1990]

I've added one comment. I'll properly test this tomorrow.

[machi1990]

I've added one comment. I'll properly test this tomorrow.

I am still seeing the error

alter table "public"."note" alter column "_id" drop not null - column "_id" is in a primary key

I used the postgres templates.

I guess it might be the fact that the the column in database has a default value while the parsed column from the schema does not. This does not go well with the diff computation.

[craicoverflow]

I am still seeing the error

Weird, you have run yarn build?

[machi1990]

I am still seeing the error

Weird, you have run yarn build?

Yes.

[machi1990]

I've added one comment. I'll properly test this tomorrow.

I am still seeing the error

alter table "public"."note" alter column "_id" drop not null - column "_id" is in a primary key

I used the postgres templates.

I guess it might be the fact that the the column in database has a default value while the parsed column from the schema does not. This does not go well with the diff computation.

I was testing the first patch and forgot to rebase over the latest change you've made today. This seems to be no longer the issue and the PR fixes the problem. Thanks for driving this baby home :-)