Introduce a Tuple object instead of Map<String,Object> and the equivalent for the association info -------------------------------------------------------------------------------------------------- Key: OGM-69 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-69 Project: Hibernate OGM Issue Type: Improvement Reporter: Emmanuel Bernard sanne other thing, you keep passing around "tuples", i.e. "Map<String, Object>" . wouldn't it be nice to make our object for that? I know we discussed it about the keys, but for objects we where unsure, depending on how it's looking in the end. but it looks like to make sense to me now.. emmanuel yes indeed, my train of thoughts is the following we will replace Cache with our own object (see Bucket discussion) and yes I think having a Tuple object would make sense as wll (same of the association info potentially Tuple and thw Association info one would record the list of changes applied (ie add / update / remove such and such column) And from this set of information the Dialect will be able to store the data accordingly 15:11 In ISPN via an AtomicMap for example I'm a little bit concerned about the overhead of creating and maintaining two sets of object in the end the Tuple and what ISPN or other dialect end up having but that might not be too problematic sannegrinovero: but I'd keep this enhancement for a different JIRA / pull-request -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira