Open beberlei opened 9 years ago
I jsut looked at the UnitOfWork code, and it just maps the missing columns as "undefined" properties of the Entity itself, so in the example above, the current case would be that $person->country
isset and saved to the object if necessary.
This is a bit magic, but changing to the described feature above would be a BC break.
I am unsure how to proceed, to make it possible working with arbitrary data in a nice way.
Column stores such as Cassandra and Azure allow to store arbitrary columns for one record. We can support that use case with a
@FieldMap
annotation on an array property in each entity.This field map would be populated with all the properties that cannot be mapped to a regular field.
Say the database has the properties:
And an entity:
Then the
country
property would be passed into thefields
.This should be done outside of the
Storage
layer, by checking for existing properties and building up an array of non mapped fields, then checking if a field map exists to write them too. Otherwise they get skipped (like they are at the moment probably).