Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7824593
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T08:38:58+00:00 2026-06-02T08:38:58+00:00

It is more of a database design question and am curious how professional database

  • 0

It is more of a database design question and am curious how professional database admins would approach when there are only two set of values – take an example below of two design scenario and which you would choose; and why?

Scenario One

 table INVOICES
 -------------------------------
 id | royalty_fee | royalty_type
 -------------------------------
 1  | 15          | percentage
 2  | 10.00       | fixed
 1  | 25          | percentage
 1  | 25.00       | fixed

or….

Scenario Two

 table INVOICES
 ----------------------------------
 id | royalty_fee | royalty_type_id
 ----------------------------------
 1  | 15          | 1
 2  | 10.00       | 2
 1  | 25          | 1
 1  | 25.00       | 2


 table ROYALTY_TYPES
 -------------------------------
 id | label
 -------------------------------
 1  | percentage
 2  | fixed
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T08:39:00+00:00Added an answer on June 2, 2026 at 8:39 am

    Approach 2 is better. Your developers can use the 2nd table ROYALTY_TYPES for lookup, also if you want to add a new type or edit/update the label of the ROYALTY_TYPES you can do it easily.
    If you edit/modify label in ROYALTY_TYPES it will require change in only one place and the table INVOICES will be unaffected

    EDIT:
    I usually look for three things with respect to database design:
    How easy it is to Add: In your first approach, you will not able to add new Royalty types if you don’t happen to have a record for invoice. I mean if you want to add a new type lets say HalfFixed for future invoices. You will not be able to do it, without getting an invoice of of type HalfFixed
    How easy it is to update Lets say if you want to update Royalty Type Fixed to ‘FIX’. If you are following first approach then you would be required to update it in multiple rows.

    How easy it is to delete Now if you want to delete a type from Royalty Types then according to your first approach you will have to run an update statement on the table and setting the particular royalty type to NULL.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This is more a question of practical database design. I've designed smaller databases before,
I am designing a product database and I have a design question. There are
My question is related to Database Design for Revisions? but more complicated. I have
This is more of a design question, I'm looking for a good approach: I
I am new to database schema design and I want to learn more about
More of a question concerning the database model for a specific problem. The problem
I have a question that is more in the realm of design, than implementation.
I'm trying to design a database model and I have a question. I need
This question is in two parts: A) Is my design wrong? If so, what
Just a general database design question - no programming, but a bit of problem

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.