Doctrine / EspoCRM installation fails on Supabase due to _text (text[]) type
🔢DB Connections🟢SQL
Hello! We are trying to use Supabase as the database backend for EspoCRM.
EspoCRM uses Doctrine DBAL internally. During installation (database schema rebuild), we encounter the following error:
Later this leads to:
From our investigation:
Doctrine does not recognize the internal PostgreSQL type _text
_text appears to be the internal array type for text[]
On a local plain PostgreSQL installation, EspoCRM installs successfully
On Supabase, the schema rebuild fails due to _text
Questions:
Why does Supabase expose _text instead of text[] in a way that breaks Doctrine DBAL?
Is there a way to configure Supabase to behave like a “plain” PostgreSQL instance (without Supabase-specific layers)?
Can we disable Supabase-specific extensions or use a clean PostgreSQL mode?
Would using a direct IPv4 connection (instead of pooler) change this behavior?
Our goal is to use Supabase purely as managed PostgreSQL for EspoCRM, without relying on Supabase Auth, Storage, or other additional features.
Any guidance on how to make Supabase fully compatible with Doctrine-based applications would be appreciated.
Thank you!
EspoCRM uses Doctrine DBAL internally. During installation (database schema rebuild), we encounter the following error:
Later this leads to:
From our investigation:
Doctrine does not recognize the internal PostgreSQL type _text
_text appears to be the internal array type for text[]
On a local plain PostgreSQL installation, EspoCRM installs successfully
On Supabase, the schema rebuild fails due to _text
Questions:
Why does Supabase expose _text instead of text[] in a way that breaks Doctrine DBAL?
Is there a way to configure Supabase to behave like a “plain” PostgreSQL instance (without Supabase-specific layers)?
Can we disable Supabase-specific extensions or use a clean PostgreSQL mode?
Would using a direct IPv4 connection (instead of pooler) change this behavior?
Our goal is to use Supabase purely as managed PostgreSQL for EspoCRM, without relying on Supabase Auth, Storage, or other additional features.
Any guidance on how to make Supabase fully compatible with Doctrine-based applications would be appreciated.
Thank you!
