question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: could not parse datamodel

See original GitHub issue

I have a recent schema (39 models) created via db pull with 3.4.2. Unfortunately no svg is created and with DEBUG=* I see this error message:

  prisma:GeneratorProcess Error: could not parse datamodel +463ms
  prisma:GeneratorProcess     at Object.exports.default [as onGenerate] (C:\Users\Jan\Documents\throwaway\cloud-api\node_modules\prisma-erd-generator\dist\generate.js:146:19) +1ms
  prisma:GeneratorProcess     at processTicksAndRejections (internal/process/task_queues.js:95:5) +0ms
  prisma:GeneratorProcess     at async LineStream.<anonymous> (C:\Users\Jan\Documents\throwaway\cloud-api\node_modules\@prisma\generator-helper\dist\generatorHandler.js:36:24) +1ms

What is the best way to debug this?

(I unfortunately can not share the schema here)

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:18 (7 by maintainers)

github_iconTop GitHub Comments

31reactions
Nypeehcommented, Apr 23, 2022

I had the same problem. “Error: could not parse datamodel”. I solved that with a simple solution above.

My directory to the folder project was:

- D:\\Projetos\\Projetos Gerais\\fullcycle-prisma\\node_modules\\prisma\\query-engine-windows.exe

Pay attention that “Projetos Gerais” has a blank space

My solution was replace that space to “_”.

- Projetos Gerais
+ Projetos_Gerais

Fixed directory

+ D:\\Projetos\\Projetos_Gerais\\fullcycle-prisma\\node_modules\\prisma\\query-engine-windows.exe

After that, the error was solved for me. I hope this can help someone.

2reactions
matteothebravecommented, Nov 2, 2022

i had the same issue and solved with

I had the same problem. “Error: could not parse datamodel”. I solved that with a simple solution above.

My directory to the folder project was:

- D:\\Projetos\\Projetos Gerais\\fullcycle-prisma\\node_modules\\prisma\\query-engine-windows.exe

Pay attention that “Projetos Gerais” has a blank space

My solution was replace that space to “_”.

- Projetos Gerais
+ Projetos_Gerais

Fixed directory

+ D:\\Projetos\\Projetos_Gerais\\fullcycle-prisma\\node_modules\\prisma\\query-engine-windows.exe

After that, the error was solved for me. I hope this can help someone.

I had the same issue and your tip solved my problem. I really appreciate

Read more comments on GitHub >

github_iconTop Results From Across the Web

VS2012 Error from Entity Data Model: "Could not parse ...
Could not parse configuration file. The error message is: 'An item with same key has already been added.'. Try editing the file manually ......
Read more >
Solved: Error Message; The search for datamodel 'abc_123'
Solved: I have two indexers in peer that share 1 index, and 1 data model. ... Error Message; The search for datamodel 'abc_123'...
Read more >
Custom Print Report Not Populating After Removing The Rich ...
"Could not able to parse datamodel xml, it is either corrupted or not ... Click on 'Data' tab > Click on 'View'; The...
Read more >
Entity Data Model: Could not parse the configuration file - MSDN
I'm getting the following error: "Could not parse the configuration file. The error message is: 'There are multiple root elements.
Read more >
pypeit.datamodel module - Read the Docs
The class itself is an abstract base class that cannot be directly instantiated. As a base class, DataContainer objects are versatile, but they...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found