Prisma studio error on latest version
# orm-help
g
Prisma studio error on latest version
r
@Gelo 👋 Could you restart and check? Also are you using the Electron app or the
prisma studio
command?
g
Hi @Ryan this is the electron app. The prisma studio command is working fine
r
Could you share screenshot of the expanded Show Details section? It's most probably because the Electron app is a version behind but I'd like to confirm
g
Copy code
Error starting Prisma Client: {
  "message": "Get config: Schema Parsing P1012\n\nerror: The preview feature \"interactiveTransactions\" is not known. Expected one of: microsoftSqlServer, orderByRelation, nApi, selectRelationCount, orderByAggregateGroup, filterJson, planetScaleMode, referentialActions, mongoDb\n  -->  schema.prisma:8\n   | \n 7 |   provider        = \"prisma-client-js\"\n 8 |   previewFeatures = [\"referentialActions\", \"interactiveTransactions\"]\n   | \n\nValidation Error Count: 1\n",
  "stack": "Error: Get config: Schema Parsing P1012\n\nerror: The preview feature \"interactiveTransactions\" is not known. Expected one of: microsoftSqlServer, orderByRelation, nApi, selectRelationCount, orderByAggregateGroup, filterJson, planetScaleMode, referentialActions, mongoDb\n  -->  schema.prisma:8\n   | \n 7 |   provider        = \"prisma-client-js\"\n 8 |   previewFeatures = [\"referentialActions\", \"interactiveTransactions\"]\n   | \n\nValidation Error Count: 1\n\n    at getConfigBinary (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:137:19|Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:137:19>)\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)\n    at async Object.getConfig (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:35:16|Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:35:16>)\n    at async Object.getGenerators (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/getGenerators.js:72:20|Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/getGenerators.js:72:20>)\n    at async PCW.getDMMF (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/node_modules/@prisma/studio-pcw/dist/pcw.js:59:42|Studio.app/Contents/Resources/app.asar/node_modules/@prisma/studio-pcw/dist/pcw.js:59:42>)\n    at async IpcMainImpl.prisma (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/build/ipc/prisma-ipc.js:26:54|Studio.app/Contents/Resources/app.asar/build/ipc/prisma-ipc.js:26:54>)"
}
Error: Error starting Prisma Client: {
  "message": "Get config: Schema Parsing P1012\n\nerror: The preview feature \"interactiveTransactions\" is not known. Expected one of: microsoftSqlServer, orderByRelation, nApi, selectRelationCount, orderByAggregateGroup, filterJson, planetScaleMode, referentialActions, mongoDb\n  -->  schema.prisma:8\n   | \n 7 |   provider        = \"prisma-client-js\"\n 8 |   previewFeatures = [\"referentialActions\", \"interactiveTransactions\"]\n   | \n\nValidation Error Count: 1\n",
  "stack": "Error: Get config: Schema Parsing P1012\n\nerror: The preview feature \"interactiveTransactions\" is not known. Expected one of: microsoftSqlServer, orderByRelation, nApi, selectRelationCount, orderByAggregateGroup, filterJson, planetScaleMode, referentialActions, mongoDb\n  -->  schema.prisma:8\n   | \n 7 |   provider        = \"prisma-client-js\"\n 8 |   previewFeatures = [\"referentialActions\", \"interactiveTransactions\"]\n   | \n\nValidation Error Count: 1\n\n    at getConfigBinary (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:137:19|Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:137:19>)\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)\n    at async Object.getConfig (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:35:16|Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/engine-commands/getConfig.js:35:16>)\n    at async Object.getGenerators (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/getGenerators.js:72:20|Studio.app/Contents/Resources/app.asar/node_modules/@prisma/sdk/dist/getGenerators.js:72:20>)\n    at async PCW.getDMMF (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/node_modules/@prisma/studio-pcw/dist/pcw.js:59:42|Studio.app/Contents/Resources/app.asar/node_modules/@prisma/studio-pcw/dist/pcw.js:59:42>)\n    at async IpcMainImpl.prisma (/Applications/Prisma <http://Studio.app/Contents/Resources/app.asar/build/ipc/prisma-ipc.js:26:54|Studio.app/Contents/Resources/app.asar/build/ipc/prisma-ipc.js:26:54>)"
}
    at ki.init (file:///Applications/Prisma%20Studio.app/Contents/Resources/app.asar/renderer/assets/index.js:1:103976)
👍 1
r
Yup, definitely due to an older version. We will release a new version on Monday 🙂 Till then you can use
prisma studio
as a workaround.