null value in not null column when using Heroku Postgres with connection pooling

[chrisdrackett]

I'm currently using Heroku with connection pooling turned on (https://devcenter.heroku.com/articles/postgres-connection-pooling#running-pgbouncer-on-a-dyno) following #503. As far as I can tell everything is working, but I do often see the following in my logs:

2020-03-21T02:30:34+00:00 app[postgres.2624]: [AMBER] [25-1]  sql_error_code = 23502 ERROR:  null value in column "createdAt" violates not-null constraint
2020-03-21T02:30:34+00:00 app[postgres.2624]: [AMBER] [25-2]  sql_error_code = 23502 DETAIL:  Failing row contains (cjzsuux87000g0779oa1bwv2l, null, null, , V0u5IMGuR1dlPjtDmPj3vNUU7, null, f).
2020-03-21T02:30:34+00:00 app[postgres.2624]: [AMBER] [25-3]  sql_error_code = 23502 STATEMENT:  UPDATE "public"."Project" SET "title" = $1, "id" = $2, "updatedAt" = $3, "createdAt" = $4, "creator" = $5, "deletedAt" = $6 WHERE "public"."Project"."id" IN ($7)

when inspecting the DB I see all columns have createdAt set, so I'm not 100% sure going on, but felt like I should report just in case its helpful!

[pantharshit00]

Sorry for the late response here.

Do you have a reproduction for this? I mean the datamodel and client call that triggers this action so that we can triage this out.

[timsuchanek]

Closing this due to inactivity.