prisma-client-go
prisma-client-go copied to clipboard
Error when database doesn't exist
When calling Connect
, the command may succeed even though the database doesn't exist. Instead, I believe we could already error here and let the user know the database needs to be migrated first, as opposed to getting an error on the first query.
Hey @steebchen. whats the update on this? i'd like to try and work on this. to prevent duplication of efforts, i need to know if there's a greenlight to work on a pull request.
Hey @steebchen. whats the update on this? i'd like to try and work on this. to prevent duplication of efforts, i need to know if there's a greenlight to work on a pull request.
Edit: also, i noticed in #279 should fix #275 but the issues are still open. i am hoping to make a few pull requests in my free time and i am not sure which issues are exactly open right now. can you explain this?
I've added a comment to #275. I'm not sure if this issue here is supposed to be implemented in the Go client directly or if we would rather do it in the internal query engine. I've added a comment to #275 since this one needs to be implemented in the go client by streaming query engine logs and parsing them I believe. If you want to send a PR for #275 let's please continue the conversion on that issue.