Currently associations are mapped to Redis with the hash dialect using native Redis lists etc. This is kind of nice, but I feel we should reconsider how the identifiers of these lists are built. Currently we have the association table name in there, but I think using the entity name "on this side" of an association makes more sense. E.g. like this:
{code}
JUG:123:members
{code}
instead of
{code}
JUG_Members:123:members
{code}
I think that'd make things more regular. I.e. an entity would be stored under a key such as "JUG:123", and the associations it maintains under keys such as "JUG:123:roleName".
Alternatively, a purely "table"-based mapping as done for ISPN and Ehcache could make sense. |
|