<p>(<em>For future me when I inevitably hit the same issue - and hopefully someone else who stumbles on this</em>)</p>
<p>I hit an error when trying to update a Prisma schema (while using <a href="https://supabase.com/">Supabase</a>). I needed to update a name of one of my columns so I ran a <code>prisma migrate</code> command (<code>npx prisma migrate dev --create-only</code>) -  (<a href="https://www.prisma.io/docs/concepts/components/prisma-migrate/migrate-development-production">link to documentation</a>) after updating the schema and got the following error -</p>
<blockquote>
<p>Error: db error: FATAL: bouncer config error
0: migration_core::state::DevDiagnostic
at migration-engine/core/src/state.rs:269</p>
</blockquote>
<h2>Solution (what worked for me)</h2>
<p>Head to your .env file and update the port of your connection string to <code>5432</code> from <code>6543</code></p>
<h3>WHY?</h3>
<p>6543 is a pooled port number which shouldn't be used when migrating, instead use the non-pooled connection string using 5432.</p>
<h3>Links</h3>
<p><a href="https://stackoverflow.com/questions/74876237/cant-migrate-schema-using-prisma-with-supabase">Stack overflow source</a></p>
<p><a href="https://supabase.com/docs/guides/integrations/prisma#connection-pooling-with-supabase">Supabase pooled port number documentation</a></p>


Phil Gebauer

Prisma Migration Error

Solution (what worked for me)

WHY?

Links