Title
j

Jaafari El Housseine

12/22/2020, 10:49 AM
I am getting this
["java.lang.UnsupportedOperationException: empty.head\n\tat scala.collection.immutable.Vector.head(Vector.scala:185)\n\tat com.prisma.deploy.connector.mysql.database.MySqlJdbcDeployDatabaseMutationBuilder.$anonfun$deleteRelationColumn$1(MysqlJdbcDeployDatabaseMutationBuilder.scala:135)\n\tat slick.basic.BasicBackend$DatabaseDef.$anonfun$runInContextInline$1(BasicBackend.scala:172)\n\tat scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:303)\n\tat scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:37)\n\tat scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)\n\tat akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)\n\tat akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:91)\n\tat scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)\n\tat scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:81)\n\tat akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:91)\n\tat akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:40)\n\tat akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:44)\n\tat akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)\n\tat akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)\n\tat akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)\n\tat akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)\n"]
Prisma 1.34 fails to run a migration. I tried all I can and still same issue. I don’t want to drop tables & re-build from scratch again
r

Ryan

12/22/2020, 12:22 PM
Hey @Jaafari El Housseine 👋 As the migration didn’t go through, could you check by dropping the last entry in the migration table and re-migrate?
j

Jaafari El Housseine

12/22/2020, 12:23 PM
I did, still same issue
r

Ryan

12/22/2020, 1:56 PM
Then unfortunately setting up from scratch would be the way to go You would need to manually bring the current schema and database in sync. Dump the SQL, do an initial migration, load the data.
j

Jaafari El Housseine

12/22/2020, 1:58 PM
😕 I did it multiple times now. Not working, the issue happens to only one Table. I tried other tables & Prisma executed correctly
@Mike B.