Hey there everyone: We have a development environment with a remote development postgres server (hence, everything which is merged into DEV trunc is running against remote PG development server). I've read the following: https://www.prisma.io/docs/guides/database/developing-with-prisma-migrate/team-development The document mentions: "Ania and Javier make additive changes to the schema in their local environment and generate migrations" Does this then recommend a developer run a shadow DB instance (local PG db) against the remote postgress instance to obtain the latest changes from the development environment in order to test/develop against? I'm trying to understand the typical prisma development workflow using a PG Appreciate anyone's feedback here 👍

Hey 👋 Does each of your developers have a remote development Postgres server? Ideally, developers can test out their schema changes in their local PostgreSQL database and then merge it into a staging/production database.

Hi @Nurul, yeah there is only one remote DEV server and the developers then have local PG instance against which they develop... I was trying to figure out if this is what the shadow database functionality was for, to easily recreate the remote schema in local PG and then develop against local db and generate migration files to add to a pull request... is this the suggested workflow for prisma...?

Shadow database is used for checking if there’s a schema drift, it essentially checks if there are any manual changes have been made to the development database.