Jay Bell
08/02/2021, 5:32 PMprisma db push
I get
{
"timestamp": "2021-08-02T17:27:04.778303482+00:00",
"level": "ERROR",
"fields": {
"is_panic": false,
"error_code": "P1003",
"message": "Database `<db name>.public` does not exist on the database server at `localhost:5432`."
},
"target": "migration_engine::logger"
}
Shouldn't it create the db if it doesn't already exist? It does on another step in CI (and locally) which is weird... the step that does not work is using docker executor and the one that does work is using ubuntu machine executor (both on circleci)
Anyone have any ideas here? I am at a loss.Jay Bell
08/02/2021, 5:34 PMdocker-compose up
) so no DBsJay Bell
08/02/2021, 5:35 PMRyan
08/03/2021, 7:18 AMlocalhost:5432
?Jay Bell
08/03/2021, 1:33 PMRyan
08/03/2021, 1:56 PMRyan
08/03/2021, 1:56 PMJay Bell
08/03/2021, 2:00 PMJay Bell
08/03/2021, 2:01 PMJay Bell
08/03/2021, 2:01 PMJay Bell
08/03/2021, 2:04 PMJay Bell
08/03/2021, 2:05 PMRyan
08/03/2021, 2:15 PMOn CI when running on an Ubuntu VM (machine executor on circleci) with docker compose up it does not workCould you share a minimal version of this setup if possible? I would like to try this out locally.
Jay Bell
08/03/2021, 2:16 PMJay Bell
08/03/2021, 2:16 PMJay Bell
08/03/2021, 2:50 PMRyan
08/03/2021, 2:53 PMdb push
?Jay Bell
08/03/2021, 2:55 PMJay Bell
08/03/2021, 2:59 PMJay Bell
08/03/2021, 3:05 PM--force-reset
flag?
https://github.com/prisma/prisma/issues/7440Jay Bell
08/03/2021, 3:06 PMJay Bell
08/03/2021, 3:19 PMJay Bell
08/03/2021, 3:52 PM.env
file from s3 prior to pushing the schemas, so the "right" db url wasn't loaded (thanks to adding DEBUG="*"
prior to the command). That being said I am very confused by that error itself, I don't think it is very descriptive as to what the problem was and I am not sure where the DB url case from that is was "trying" to use before.Ryan
08/04/2021, 7:00 AM