One address table for many types of addresses I have an application where I have to store adresses of multiple types of location.

For example, my app requires addresses of people, hotels and event venues. 

Should I create separate tables for different type of addresses having same fields? or Should I add an additional field telling what is the type of address?
Unless the attributes between the different types are totally different (which I doubt), go for the second option and store the address type in a column of the address table.