DDC-3925: 1 Property -> N columns and also the reverse #4803

New Issue

admin · 2026-01-22T14:49:40+01:00

admin commented

2026-01-22 14:49:40 +01:00

Originally created by @doctrinebot on GitHub (Sep 30, 2015).

Originally assigned to: @guilhermeblanco on GitHub.

Jira issue originally created by user @guilhermeblanco:

NOTE: Similar concept to Embeddable, very different solution though

Assume I have a VO (\DateTime instance) that I want to store in 3 DB columns: datetime, timezone, milliseconds.

We should be able to map a single property that stores 3 columns and whenever we set a value for the ORM property, we store these 3 fields individually.

When reading these 3 columns, we'd also do the reverse... based on 3 column values build a single property value.

Also, we could potentially support part querying on DQL (let's say WHERE milliseconds > 50 using my example)

Originally created by @doctrinebot on GitHub (Sep 30, 2015). Originally assigned to: @guilhermeblanco on GitHub. Jira issue originally created by user @guilhermeblanco: NOTE: Similar concept to Embeddable, very different solution though Assume I have a VO (\DateTime instance) that I want to store in 3 DB columns: datetime, timezone, milliseconds. We should be able to map a single property that stores 3 columns and whenever we set a value for the ORM property, we store these 3 fields individually. When reading these 3 columns, we'd also do the reverse... based on 3 column values build a single property value. Also, we could potentially support part querying on DQL (let's say WHERE milliseconds > 50 using my example)

admin added the New Feature label 2026-01-22 14:49:40 +01:00

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#4803