Jira issue originally created by user @beberlei:
Sometimes you want to save arbitrary information for an entity using a key -> value array-structure. JPA supports this by means of the @ElementCollection annotation with allows to specify HashMaps for example.
I propose a new AssocationMapping called "ElementMapping" / "ElementCollection" and annotations (options):
The key and value definitions are necessary for converting and schema generation.
The implementation would make use of the PersistentCollection at all times and work as any other persistent collection just with primitive types.
Restrictions for a first implementation:
$entity->options['foo'] = 'bar';
$entity->options['bar'] = 'baz';
This could be done for 2.0 imho, adding the necessary changes and optimizations could then be scheduled for 2.1
Comment created by @beberlei:
In this implementation Schema-Tool would generate a table:
elementTable (entity_id-1, ..., entity_id-n, key, value) and using the Platform Type Generation of keyType and valueType
Column Names should be Change-able also since there could be people who name their primary keys "key" and "value" o_O
Ordering could be implemented on top of this using the @OrderColumn JPA implementation by adding another column to the table with a numeric order that will be "order by"'d on select time.
Comment created by myknbani:
Any news on this? It has been almost 3 years since its last update =)