Skip to main content
Software Engineering

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.

4
  • Thanks for the answer, but the problem I have with this idea is there is other information associated with the transaction that is not split like Date, Tags, Comments, AccountId etc... Commented Oct 30, 2014 at 16:37
  • Also I don't really understand the purpose of "SplitLineID". This looks like it's used to store the order of the split amounts? I don't think I care about the order though? Commented Oct 30, 2014 at 18:39
  • 1
    You could put the other information (Date, Tags etc) into a TransactionHeader table, and the table I've described would be a TransactionDetails table. And thinking about your other comment, yes, you won't need the SplitLineID field unless you want to keep the items in order. Commented Oct 31, 2014 at 9:54
  • Wouldn't this be exactly the same as the second example in my original question then? Not that that is necessarily bad, as I was leaning toward that option. Commented Oct 31, 2014 at 10:17