Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Your first proposition seems good, but I have to make extra processing and extra request to get the user information for the TRANSFER event. For example, I have this record : { created_at: "XX-XX-XX", type : "transfer", from: 21, to: 42 }, since it's a raw string, I can't enforce id constraints neither join mechanics. Commented Dec 9, 2015 at 21:41
  • Yes, but I have already mentioned in the answer that you probably do not need those. But if you do, then that proposition is not for you. Consider the other proposition. Commented Dec 9, 2015 at 21:43
  • Well that's not really what I want. I think I didn't express myself right. I will update my post. Commented Dec 9, 2015 at 22:01
  • Aha, I see. Well, there may be no solution which is not clunky, and my first proposition might still represent the least amount of clunkiness, but you are to decide that. Commented Dec 9, 2015 at 22:23
  • 1
    Well, that's what I thought... All looks clunky. I will left this answer open few days. Thanks for your help Commented Dec 9, 2015 at 22:28