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.
init error: Datasource provider not known
See original GitHub issueError: Schema parsing
error: Datasource provider not known: "to_be_defined".
--> schema.prisma:2
|
1 | datasource management {
2 | provider = "to_be_defined"
|
Validation Error Count: 1
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
prisma init --url does not like mongodb+srv:// #9644 - GitHub
prisma init --url does not like mongodb+srv:// #9644 ... Error: P1012: error: Datasource provider not known: "mongodb+srv".
Read more >Resolving Failed to Configure a DataSource Error - Baeldung
In this short tutorial, we'll discuss what causes and what resolves the “Failed to configure a DataSource” error on a Spring Boot project....
Read more >Unable to initialize system Data Source provider
I've tried to replace all org.wso2.carbon.ndatasource libraries with older version (from 6.2.0) but nothing seems to work. Any idea ? Thank you ...
Read more >Cannot initialize the data source object of OLE DB provider ...
The error message is: The OLE DB provider "MSDASQL" for linked server "IP21" reported an error. The provider did not give any information...
Read more >WebSphere Datasource Test connection failed with ... - IBM
Solution : 1) Make sure you have restarted the Deployment Manager and the nodeagent after creating the J2C auth alias. · Example Exceptions:...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you for raising this issue 🙏 I am able to replicate it. I’ll fix this ASAP
Ohh right… I think it was related with the missing version
2.0.0-beta.2of@prisma/client.it’s working now. Thanks!