Tag: this method seems to have lost a lot of the built in checking options possible with separate transaction tables where I can ensure

Database Development

Am I over normalizing?

Suppose a payments transaction system where the transactions can be between users on the platform (Customer-Customer, Customer-Merchant, Merchant-Merchant) and users AND the platform (Customer-Platform, Merchant-Platform for top-ups/withdrawals/fees etc.). Users: User |user_id|basic user information| Customer |uses basic User model| Merchant |merchant_id|user_id|other merchant fields| Wallets: Wallet |wallet_id|balance| UserWallet |wallet_id|user_id| MerchantWallet |wallet_id|merchant_id| Since transactions might not always be […]

Tags Customer-Merchant, for example, I've found the large transaction table could be normalized further by splitting the halves of the transaction and crediting the base wallet i, it also means that the joins are much more complex and heavy. Am I overdoing it? Would really appreciate the help., Merchant-Merchant) and users AND the platform (Customer-Platform, Merchant-Platform for top-ups/withdrawals/fees etc.). Users: User |user_id|basic user information| Customer |uses basic User model| Merch, repeat it across all the transaction tables and merge the results then return it. While this would mean much smaller individual tables to que, Suppose a payments transaction system where the transactions can be between users on the platform (Customer-Customer, that a Merchant-Merchant transaction type would be referenced to two Merchant wallets. The original method was to have multiple transaction t, this method seems to have lost a lot of the built in checking options possible with separate transaction tables where I can ensure