Why are addresses saved in both Nop_Address and Nop_CustomerAttribute?

Can someone please explain why a customer address is saved in both Nop_Address and Nop_CustomerAttribute?

I may be wrong but in my opinion it should only be saved in Nop_Address.

Does anyone have some input on this?  I'd also like to know the logic behind this.  A customer's billing and shipping info are stored in Nop_Address, so why the extra address in Nop_CustomerAttribute?

staeri wrote:

Nop_CustomerAttribute stores the original customer address. Nop_Address is like an address agenda or  where the customer can add and remove various shipping and billing addresses. The first address added to this agenda is the original customer address, BUt in Nop_Address  can be erased while the original (Nop_CustomerAttribute) can only be udated (never erased)