Re: Best way to design table to store attributes?

From: -CELKO- <jcelko212_at_earthlink.net>
Date: Sat, 24 Jan 2009 08:26:56 -0800 (PST)
Message-ID: <c4d8e128-aeb4-4c82-a330-dc749668509d_at_v5g2000prm.googlegroups.com>

-As I recall, there is a standard code for destinations in the travel industry, so you would have a two-column, 5NF table with (customer_id, destination_code) as the key and name it something like Vacations. Received on Sat Jan 24 2009 - 17:26:56 CET

This message: [ Message body ]
Next message: Mark S. (UK): "Re: Design question"
Previous message: Mark S. (UK): "Design question"
Maybe in reply to: carl.henthorn_at_gmail.com: "Best way to design table to store attributes?"
Next in thread: patrick61z_at_yahoo.com: "Re: Best way to design table to store attributes?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message