context in this discord thread.

I just created a thread in the discord then saw that we have a new community forum; figured I would move the discussion here instead.

---

Hey all, I noticed a small (but breaking in a few of my apps) change between the legacy databases and the new service based databases created by the migration tool. Specifically in the "protocol" portion of the DATABASE_URL .

The issue

It seems in the legacy databases, the DATABASE_URL variable started with postgresql://... while the new service databases default to postgres:// for the "protocol" piece of the connection string.

In particular this broke my Python-based flask apps that

1. used PostgreSQL for a database
2. used SQLAlchemy as an ORM

What I did to fix it

• Compared the two variables in vscode
• Noticed the legacy started with postgresql and new database started with postgres
• Changed the variable back to the postgresql format in my new database service
• Restarted all services that relied on that variable.

What I expected to happen

Ideally, I would hope the migration tool would match whatever format/syntax your project is using for variables in the legacy database/plugin.