Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postgres: A database with that name doesn't exist at xx.xx.xx.xx using @2.0.0-preview013.3 #694

Closed
emolr opened this issue Oct 9, 2019 · 10 comments
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/regression A reported bug in functionality that used to work before.
Milestone

Comments

@emolr
Copy link

emolr commented Oct 9, 2019

Trying to run prisma2@2.0.0-preview013.3 dev

It works fine with v2.0.0-preview-13.2, but when running with v2.0.0-preview013.3 i get this error in the terminal:

Screenshot 2019-10-09 at 07 48 10

The dataabse postgres is available on the server, thus no problem using a previous version of prisma2.

Note!
I'm running a postgres database on google cloud.
Running on MacOS latest

Thanks for the great work!

@janpio janpio added the kind/regression A reported bug in functionality that used to work before. label Oct 9, 2019
@janpio
Copy link
Member

janpio commented Oct 9, 2019

To confirm: The exact same setup (postgres on google cloud, running macOS latest) works with 2.0.0-preview-13.2 but not 2.0.0-preview013.3 when running prisma dev?

@christopherschroer
Copy link

I'm running into the same issue running prisma2 dev on ubuntu 19.04 while using prisma2@2.0.0-preview013.3 with a postgres database provided by Heroku. I was following the instructions on the tutorial linked in the README.md

@alexwine36
Copy link

Same issue on Windows 10 with 2.0.0-preview013.3
Running prisma2 lift save

@janpio
Copy link
Member

janpio commented Oct 9, 2019

@christopher-schroer @alexwine36 So you both are experiencing a mistaken error message that a database with a name does not exist, although it does exist, correct?

@christopherschroer
Copy link

@janpio yes

@emolr
Copy link
Author

emolr commented Oct 10, 2019

To confirm: The exact same setup (postgres on google cloud, running macOS latest) works with 2.0.0-preview-13.2 but not 2.0.0-preview013.3 when running prisma dev?

yes, i can confirm this :)

@pantharshit00
Copy link
Contributor

I can confirm this regression. I tested on a heroku postgres instance and as reported by @emolr version 2.0.0-preview-13.2 works but the latest version 2.0.0-preview-013.3 doesn't.

I also tested with the latest alpha(prisma2@2.0.0-alpha.232, binary version: 19ed9db8b704a89eef6fe710fa52c2ad0493443f) and it also fails

@janpio janpio added bug/2-confirmed Bug has been reproduced and confirmed. process/candidate labels Oct 10, 2019
@divyenduz
Copy link
Contributor

divyenduz commented Oct 11, 2019

Internal note: Needs to be discussed from spec's perspective

  • This is broken right now though, we should fix it without being blocked on spec.

@divyenduz
Copy link
Contributor

The spec part of this issue is tracked here: prisma/specs#244

@timsuchanek
Copy link
Contributor

Thanks a lot for reporting. Fixed in latest preview.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/regression A reported bug in functionality that used to work before.
Projects
None yet
Development

No branches or pull requests

7 participants