Thank your very much Ben,
And those are good questions to address the problem. My answer is a bit of both. We need someone to blame (user actions) and what did they do (changes to the rows). I can propose the final user just to have a limited information about user information but knowing the users they always want more so I am planning for the hole enchilada.
So you are stating a very important issue and that’s what happens when a action/transaction touches multiple tables… still not sure how am I going to address this use case but carbonite seams appealing.
I will review the bytepack solution proposed by @jeroenvisser101 and carbonite suggested by @kartheek .
Guys, do you think this is a common “problem”? do you think Ecto should have an API to address it? What do you think?
Thanks again, best regards.
Joaquin Alcerro
