What are the [dis]advantages of using a key/value table over nullable columns or separate tables?
问题 I'm upgrading a payment management system I created a while ago. It currently has one table for each payment type it can accept. It is limited to only being able to pay for one thing, which this upgrade is to alleviate. I've been asking for suggestions as to how I should design it, and I have these basic ideas to work from: Have one table for each payment type, with a few common columns on each. (current design) Coordinate all payments with a central table that takes on the common columns