Databases
StackOverflow2013
Postsdbo
PODatabase Architecture for "Badge" System & Arbitrary Criteria (MySQL/PHP)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODatabase Architecture for "Badge" System & Arbitrary Criteria (MySQL/PHP)
    primarykey
    data
    text
    <h3>Quickie-Question:</h3> <p>To summarize, I'm a little confused as to how I would design such a database that allows indefinite badge-rule creation without requiring structural changes to the previously existing user-tables in the database.</p> <p>Storing Badge Title, Criteria, etc. What would that Table look like?</p> <ul> <li>badge_id (1)</li> <li>badge_title (10K Badge)</li> <li>badge_image (10k.jpg)</li> <li>badge_criteria ([posts] >= 10000)<br/> <code>...</code></li> </ul> <h3>Winded-Question:</h3> <p>I would like to implement a badge-system on my own personal projects, but am seeking a bit of advice as to how one would best do such a thing. I've been reading some of the questions here about badge-systems, but don't see the database-architecture getting much attention.</p> <p>Badges that are based on user-points (Hypothetical "10k Badge") would seem pretty straight forward. Any event that affects the users reputation (upvotes, downvotes, answer-accepted, etc) would invoke a method to review the users new reputation, and potentially award a badge.</p> <p>That system sounds pretty straight forward, but what does that look like as a database for the administrator who wants to create innumerable amounts of badges with little-effort down the road - some of which may be based on different criteria, and not simply the user reputation.</p> <p>User-reputation is likely a value within the user-record itself. But ideally, wouldn't you want to avoid having to add new fields to the user table when you create new badges? For instance the "Edited 100 Entries" badge - you wouldn't create a new column "entries_edited" within the Users Table, would you? And then increment that after each entry-edited...</p> <p>Any hints?</p> <p>Stackoverflow Archive:</p> <ul> <li><a href="https://stackoverflow.com/questions/522943/best-way-to-store-badge-criteria">Best way to Store Badge Criteria</a> <strong>(Not a duplicate)</strong></li> <li><a href="https://stackoverflow.com/questions/314412/designing-a-badge-system-where-to-fire-business-logic-in-code-or-stored-procedu">Designing a Badge System: Where to fire business-logic?</a></li> </ul> <hr> <p><em>Note: I'm NOT asking how to associate badges with users. I'm NOT asking how to award badges (that will be done programmatically)</em> </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USSampson
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODatabase Architecture for "Badge" System & Arbitrary Criteria (MySQL/PHP)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODatabase Architecture for "Badge" System & Arbitrary Criteria (MySQL/PHP)
      1. USRobert S.
      1. VTFavorite
    3. VO
      singulars
      1. PODatabase Architecture for "Badge" System & Arbitrary Criteria (MySQL/PHP)
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 as I am looking for the same answer.
      singulars
      1. PODatabase Architecture for "Badge" System & Arbitrary Criteria (MySQL/PHP)
      1. USRobert S.
 

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