Schema Tool keeps recreating table user when inside a schema in PostgreSQL #7494

New Issue

admin · 2026-01-22T15:52:18+01:00

admin commented

2026-01-22 15:52:18 +01:00

Originally created by @ThomasLandauer on GitHub (Apr 6, 2025).

Bug Report

Q	A
Version	3.3.2

Summary

With the following mapping:

#[ORM\Table(schema: 'my')]
class User

whenever I rerun bin/console make:migration, I'm getting:

$this->addSql('CREATE TABLE my."user" (...)');
$this->addSql('DROP TABLE my."user"');

This is apparently due to user being a reserved word in SQL (or PostgreSQL), and the escaping Doctrine applies (as discussed in various issues at DBAL).

When I remove the schema, it works as expected:

[WARNING] No database changes were detected.

Workaround:
Rename the table in the database:

#[ORM\Table(name: 'users', schema: 'my')]

Current behavior

Expected behavior

How to reproduce

Originally created by @ThomasLandauer on GitHub (Apr 6, 2025). ### Bug Report  | Q | A |-------------------------------------------- | ------ | Version | 3.3.2 #### Summary With the following mapping: ```php #[ORM\Table(schema: 'my')] class User ``` whenever I rerun `bin/console make:migration`, I'm getting: ```php $this->addSql('CREATE TABLE my."user" (...)'); $this->addSql('DROP TABLE my."user"'); ``` This is apparently due to `user` being a reserved word in SQL (or PostgreSQL), and the escaping Doctrine applies (as discussed in various issues at DBAL). When I remove the schema, it works as expected: > [WARNING] No database changes were detected. Workaround: Rename the table in the database: ```php #[ORM\Table(name: 'users', schema: 'my')] ``` #### Current behavior  #### Expected behavior  #### How to reproduce

admin referenced this issue

2026-01-22 16:07:49 +01:00

[PR #7494] Do not allow cache clearing with APCu #10520

Sign in to join this conversation.