Basic pseudo class layout below...
class Location(): # Class containing information about a location. id address_one class CustomerLocation(Location): customer_id account_rep class VendorLocation(Location): vendor_id drop_ship_cut_off_time
Let's say you have locations which are going to be used to store location info for customers and vendors.
What would be the pro's/cons of the three options in how they relate to application maintenance and extensibility...
- One large table containing all fields.
- One large table containing all common fields with related tables containing specialized information about the large table records.
- Many small tables containing all fields related to specific uses.CustomerLocation table VendorLocation without using a "master table" for common fields.