Date: 05/04/01
- Next message: darcy w. christ: "[phplib] login before logout"
- Previous message: HurricaneIndy <email protected>: "[phplib] OT: Database Design, THANKS"
- In reply to: HurricaneIndy <email protected>: "[phplib] OT: Database Design"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Assuming that your customer information is fairly standardized, I'd use a
"Domains" table with a domain id, and a customer id, and a "Customers" table
which only contains a customer id.
That way, you can associate as many domains as you like with a customer.
_alex
-- alex black, ceo enigma <email protected>the turing studio, inc. http://www.turingstudio.com
vox+510.666.0074 fax+510.666.0093
--------------------------------------------------------------------- To unsubscribe, e-mail: phplib-unsubscribe <email protected> For additional commands, e-mail: phplib-help <email protected>
- Next message: darcy w. christ: "[phplib] login before logout"
- Previous message: HurricaneIndy <email protected>: "[phplib] OT: Database Design, THANKS"
- In reply to: HurricaneIndy <email protected>: "[phplib] OT: Database Design"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

