Hello, I have used the *easiest approach first: put all the address fields in the "candidate" table.*Even the second approach is possible. But should i keep 2 seperate tables for both address types...
Thanks... On Mon, May 14, 2012 at 10:57 PM, pbreit <[email protected]> wrote: > Consider the easiest approach first: put all the address fields in the > "candidate" table. > > If you have good reason to believe this is not the DB design you want, > then consider a separate "address" table. That will complicate the code a > bit because you'll need to program the logic to link the address to a > candidate. >
