Add column to table without related property on its entity #5398

New Issue

admin · 2026-01-22T15:06:27+01:00

admin commented

2026-01-22 15:06:27 +01:00

Originally created by @koemeet on GitHub (Jan 30, 2017).

Originally assigned to: @Ocramius on GitHub.

I wanted to implement multi tenancy for an existing project using Doctrine without changing their metadata files or subclassing their models to add an extra field. Would it be easy/possible to extend Doctrine in a way that it adds a specific column to the table of an entity without having a property on that entity that represents that column? This way the models stay intact and you could use a SQL filter to filter down on that column to achieve multi tenancy.

Are there people who implemented something similar or have tips on how this can be done with Doctrine ORM?

Originally created by @koemeet on GitHub (Jan 30, 2017). Originally assigned to: @Ocramius on GitHub. I wanted to implement multi tenancy for an existing project using Doctrine without changing their metadata files or subclassing their models to add an extra field. Would it be easy/possible to extend Doctrine in a way that it adds a specific column to the table of an entity without having a property on that entity that represents that column? This way the models stay intact and you could use a SQL filter to filter down on that column to achieve multi tenancy. Are there people who implemented something similar or have tips on how this can be done with Doctrine ORM?

admin added the Improvement Can't Fix Question labels 2026-01-22 15:06:27 +01:00

admin closed this issue

2026-01-22 15:06:28 +01:00

admin commented

2026-01-22 15:06:32 +01:00

@Ocramius commented on GitHub (Jan 30, 2017):

You'd just add a column in a manual migration: this is not something that can be done in the metadata API, since every field expects a matching reflection field.

@Ocramius commented on GitHub (Jan 30, 2017): You'd just add a column in a manual migration: this is not something that can be done in the metadata API, since every field expects a matching reflection field.

admin commented

2026-01-22 15:06:33 +01:00

@koemeet commented on GitHub (Jan 30, 2017):

Thanks for the fast response, wow! 😄

@koemeet commented on GitHub (Jan 30, 2017): Thanks for the fast response, wow! 😄

admin commented

2026-01-22 15:06:34 +01:00

@lcobucci commented on GitHub (Jan 31, 2017):

@steffenbrem sometime ago I've created something based on Doctrine\DBAL\Sharding\PoolingShardConnection and a custom Doctrine\DBAL\Sharding\ShardChoser\ShardChoser to implement multitenancy but I had a different schema for each tenant (with the same mapping) and everything worked just fine.

@lcobucci commented on GitHub (Jan 31, 2017): @steffenbrem sometime ago I've created something based on `Doctrine\DBAL\Sharding\PoolingShardConnection` and a custom `Doctrine\DBAL\Sharding\ShardChoser\ShardChoser` to implement multitenancy but I had a different schema for each tenant (with the same mapping) and everything worked just fine.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#5398