David Beroff (d4b) wrote,
David Beroff

CREATE TABLE Transaction...

CREATE TABLE Transaction (...) ENGINE = InnoDB, COMMENT = 'A Transaction is a transfer of value to or from a given Member.';
It took me a few hours, but I think I managed to encapsulate the essence of traditional double-entry bookkeeping into a single Transaction table. This process is definitely an exercise in trying to predict precisely how much detail is sufficient to get the job done correctly, while leaving hooks for potential future extensibility, without going overboard: Should there be a column for PayPal's (or other intermediary's) transaction identifier? Probably. The rest of their data? Probably not; those could always be found on PayPal if need be. Or maybe just throw that all into a blob, and move on. Is a Service column overkill, if I'm only planning on one type of paid service? Maybe... until one considers that some people's "paid" service will actually be lifetime accounts, (i.e., without making monthly payments), and then there's the affiliate program, and advertising, and....
Tags: mtat, webdev
  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.