Lookup table explained
What is the meaning of a lookup table, from an Oracle point of view?

    Requires Free Membership to View

    By submitting your registration information to SearchOracle.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchOracle.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

What other point of view would there be? :)

Anyway, I'd call a lookup table any table that was created to hold mostly static data and is used to assist in normalizing your database design. For instance, if I create a state_lookup table that contains two columns: state_code and state_name. I now have the ability to store the state_code in any other table I want and retrieve the state_name from the "lookup" table as needed (via a join).

I don't think there's an "Oracle definition" of lookup table in particular. The concept of a lookup table is more a design/programming term than something that is a vendor specific term.

For More Information


This was first published in April 2003

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.