mikkelsl
08/20/2020, 11:07 AMed
08/20/2020, 5:58 PMREADME.md
is generated in a migration. I’ve had a case where the SQL in the README.md
included some ALTER TABLE _table_ …
but were not in the steps.json
file. So when I ran the migrate up
, the table was not altered as advertised in the README.md
. Is this a bug or is there something with our setup that could have caused this?jknr
08/21/2020, 9:10 AMSpencer Curry
08/21/2020, 3:28 PMJonathan
08/26/2020, 1:27 PMTim Leslie
08/28/2020, 1:22 AM2.6.0-dev.44
) when running migrations. I can run my initial migration and see the _Migration
table get correctly populated with the appropriate info. I then change my schema, generate and run a second migration. The migration run successfully, the database is updated as expected, all the commandline output is 🚀 , but now my _Migration
table is empy. I would expect to see two entries, but I’m seeing zero. Has anyone else seen this happen? Should I submit a bug report?Tim Leslie
08/31/2020, 12:58 AM2.6.0-dev47
, where specifying a particular schema
name in my postgres database causes the initial migration not to run at all:Wade Tandy
09/11/2020, 5:01 PMJosef Henryson
09/16/2020, 12:04 PMPascal
09/22/2020, 8:59 AMAlberto Perdomo
mikkelsl
09/25/2020, 4:59 PMMikastark
09/29/2020, 2:53 PMed
10/06/2020, 5:53 PMjknr
10/13/2020, 11:02 AMJosef Henryson
10/20/2020, 6:59 AMFile
ADD UNIQUE (logoCompany
);
but there is no field/column called logoCompany on File, so I get this error:
Key column ‘logoCompany’ doesn’t exist in table
Any ideas on how I can proceed from this state? Do I have to manually add the field and populate it with values?
Or can I put the unique constraint on the Company field ‘logotype’ instead?
Thanks 🙏🏼uzu
10/21/2020, 9:15 AMPierre Ortega
10/21/2020, 6:21 PMBrian Bancroft
10/22/2020, 4:04 PMAlberto Perdomo
Jonathan
10/30/2020, 5:52 PMMaciek K
11/10/2020, 4:52 PMMarvin
11/20/2020, 8:59 PMprisma migrate
(new migrate) can handle renaming of models & fields?Dmitry Petrov
11/26/2020, 12:24 AMnpx prisma migrate save --experimental
relating to the virtual side of a relation being required. After updating the schema.prisma
file accordingly, it still gives me the same errors. Are there any additional steps I need to take? Has anyone else experienced this?Dmitry Petrov
11/26/2020, 12:47 AMjknr
12/07/2020, 6:12 PMMarvin
12/09/2020, 6:36 PMprisma migrate
programmatically by importing and calling a function from some of the @prisma
packages? I currently use execa
and run the command but I'm just curious if there is a better way to do that. 🙂Daniell
12/17/2020, 3:25 PMDATABASE_URL=$(heroku config:get DATABASE_URL -a foodsy-db) prisma migrate dev --create-only --preview-feature
Error: A migration failed when applied to the shadow database:
Database error: Error querying the database: db error: ERROR: permission denied to create database
Can I create the db manually? Or am I supossed to run deploy for this use case? 🤔Zarazas
12/17/2020, 4:43 PMprisma migrate reset --preview-feature
as part of my testing suite to reset my db, however running it with exec
results in:
Error: Command failed: prisma migrate reset --preview-feature
Error: We detected that your environment is non-interactive. Running this command in not supported in this context.
Is there a way to circumvent this or run the reset programmatically?