>It depends on what the data is being used for. If you want to know
>what address an order was shipped to then you need the historical
>address info. If all you need is the current customer address,
>because, say, you're sending out holiday cards, then you might not
>need to keep an old address.
Indeed.
>Martin's explanation didn't say anything about deleting the data.
Same here ;-)
>Your idea isn't a bad one, although I shy away from boolean flags
>because you have to be careful about the indexes for it.
Exactly, I dislike them as well.
One solution could be:
addresses
-customerID
-addresID
and in customers:
-CurrentAddressID
to keep the current active address.
Martijn Tonies
Database Workbench - development tool for MySQL, and more!
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com
-Sheeri
On 5/19/06, Jay Blanchard <jblanchard@stripped> wrote:
> [snip]
> > Well, one reason could be, for example, that the address changes
> > over time and they want to know what address the customer was
> > when the order was processed.
> [/snip]
>
> So you would delete an old customer address in favor of a new one? I
> would rather have an 'active/inactive' column with an accompanying date
> stamp.
>
