Databases
StackOverflow2013
Postsdbo
POHow would you design this DB?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow would you design this DB?
    primarykey
    data
    text
    <p>We are launching a website (paid subscription) and the sign up process includes entering an activation code. Activation codes are printed on scratch cards and sold via offline channels. Some of these cards are for 1 month access. Others are for 3 months and 1 year. Activation codes are unique 10-digit random numbers.</p> <p>When the access expires, users can buy another activation card and extend the subscription by entering the new activation code. Additionally, we should also be able to extend their subscription if they request for it. For example, until a certain date (e.g. 1 additional week).</p> <p>Considering the above information, how would you design the DB for the user-activation_code relationship? Do you think this design is good?</p> <pre><code>tbl_user ---------------- id name status_id tbl_user_status ---------------- id description tbl_activation_code ---------------- activation_code activation_code_type_id activation_code_status_id user_id activated_date expiry_date tbl_activation_code_type ---------------- id description tbl_activation_code_status ---------------- id description </code></pre> <p><strong>Update</strong>: Activation codes will be required only:</p> <p>1) Upon initial sign up</p> <p>2) Closer to the access expiry date (say, 7 days) when the system displays a notification with a link to page to enter the activation code</p> <p>3) After expiry, when a user tries to login, she will be asked for the activation code</p> <p>Therefore, a user is not expected to key in the activation code as and when wanted.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNuku
    1. USNuku
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow would you design this DB?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for "random numbers". there are still so many fools out there who use a sequence here :(
      singulars
      1. POHow would you design this DB?
      1. USAaron Digulla
    2. COMake sure the random number space is big enough otherwise I may be able to guess them, this means having 100-1000 times the address space you need (so 3-4 extra digits). So for you it sounds like you could safely issue a few million/tens of millions of cards, something to keep in mind.
      singulars
      1. POHow would you design this DB?
      1. USKurt
    3. COKurt, do you mean with 10-digit trandom codes I can "safely issue a few million/tens of millions of cards"?
      singulars
      1. POHow would you design this DB?
      1. USNuku
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload