Prisma 2 is failing to migrate remote database (DO hosted instance)

[pantharshit00]

I tried to perform migration in a Digitalocean hosted instance in order to triage this issue: #556

I used the default script starter

But the migration failed with the following rust panic:

Connection string:

postgresql://doadmin:XXXXXXXX@XXXXXXXXXXXX.db.ondigitalocean.com:25060/defaultdb?schema=issue_552&sslmode=prefer

Internal note: You can find the credentials in 1password.

[tomhoule]

The error message should improve after prisma/prisma-engines#45.

I've done some digging and the issue seems to be caused by the absence of a default database named postgres in DigitalOcean managed postgres. The default database name appears to be completely configurable. But at the moment prisma 2 assumes there is a default database called postgres we can log into to issue commands like CREATE DATABASE. Relevant code.

There's an always-present template1 database in postgres but it doesn't guarantee it would work for what we want to do from it, so I'll wait until I can reproduce the issue with the database from the description.

[tomhoule]

Implemented solution: try to connect to postgres, then template1 (should always be there), and failing that return with a descriptive error message. PR: prisma/prisma-engines#51

I haven't been able to reproduce the 'schema with underscore fails to migrate' issue locally, I'll try later on DO.

I'll start investigating the pgBouncer issue.

[tomhoule]

From the digitalocean doc, it looks like database creation is pretty locked down and it's meant to be done through their UI. I will keep researching, but we may have to resort to just having a good error message there.

On an existing DO database with pgBouncer, I didn't encounter any issue migrating with a schema with underscores in its name.

[divyenduz]

I was able to create database and schema using tableplus with or without pgbouncer.

I used to doadmin user to perform these operations.

[divyenduz]

@pantharshit00 I am no longer able to reproduce this error with the latest alpha, are you? If no, please close this issue.