This is great! I like the dbdiagram.io tool you using to declare SQL and generate a diagram - pretty cool.
I have just one suggestion, your payment_details table. I would have a second table or a few extra columns just to catch more meta information from the payment gateway provider.
Depending on the provider, if a payment fails - they tend to give you some additional log information which is important to store for later recon. Even with success payments, the recon information can be useful for generating reports.
Creative and energetic Software Engineer with 3 years of experience full of challenges, difficulties, and achievements. Love learning new things and teaching others and developing software.
I’m glad that you find the dbdiagram.io tool helpful to you and appreciate your suggestion about the payment_details table, it’s nice suggestion I will keep in mind next time 😀
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is great! I like the dbdiagram.io tool you using to declare SQL and generate a diagram - pretty cool.
I have just one suggestion, your payment_details table. I would have a second table or a few extra columns just to catch more meta information from the payment gateway provider.
Depending on the provider, if a payment fails - they tend to give you some additional log information which is important to store for later recon. Even with success payments, the recon information can be useful for generating reports.
I’m glad that you find the dbdiagram.io tool helpful to you and appreciate your suggestion about the
payment_detailstable, it’s nice suggestion I will keep in mind next time 😀