Home > Archive > MS SQL Data Warehousing > November 2006 > Designing db with Payment Method









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Designing db with Payment Method
Junimation

2006-11-07, 7:12 pm

What is the best design approach when designing a db that uses multiple
payment methods.

For example....

Customer will be able to use:
Credit Card
Check

Now, both of these methods have different data that needs to be collected.
Should I,
1. Design two separate entities
2. Design one entity with general attributes for both methods
3. Does the entities need to be related in anyway to each other if a
separation is used.

Thank you for your help.


--
Jorge -- MCP
Web Application Developer
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com