User login

Home ›
 CMT database schema, mark II

CMT database schema, mark II

Submitted by Benjamin Melançon on July 8, 2007 - 7:20pm
in

cmt_term_description
vapi_id : corresponds to votingapi content_id
tid : same as in term_data
description : same as in term_data. Don't see a reason to put a key on description

cmt_term_weight
vapi_id : corresponds to votingapi content_id
tid : same as in term_data
weight : same as in term_data

name (inserted into synonym-modeled table cmt_term_name, where votes for names are tracked)
LEFT OUT: vid (for now, cannot vote on what vocabulary a term belongs in)

cmt_term_hierarchy
vapi_id : corresponds to votingapi content_id
tid : same as in term_hierarchy
parent : same as in term_hierarchy

cmt_term_node
vapi_id
nid
tid

cmt_term_name (based on term_synonym table)
vapi_id
tid
name

cmt_term_description
vapi_id : corresponds to votingapi content_id
tid : same as in term_data
description : same as in term_data. Don't see a reason to put a key on description

cmt_term_weight
vapi_id : corresponds to votingapi content_id
tid : same as in term_data
weight : same as in term_data

name (inserted into synonym-modeled table cmt_term_name, where votes for names are tracked)
LEFT OUT: vid (for now, cannot vote on what vocabulary a term belongs in)

cmt_term_hierarchy
vapi_id : corresponds to votingapi content_id
tid : same as in term_hierarchy
parent : same as in term_hierarchy

cmt_term_node
vapi_id
nid
tid

cmt_term_name (based on term_synonym table)
vapi_id
tid
name

Comments

Forgot to list an important one there

Submitted by Benjamin Melançon on July 9, 2007 - 7:34am.

Forgot to list an important one. Also, vapi_id is now called content_id so it matches what votingapi itself calls it.

cmt_term_merge
content_id : key for votingapi content_id
tid1 : term, that gets to keep its name and info, to merge onto tid2
tid2 : term, that subsumes its name and info, to merge into tid1
-- I will not be able to resist deriving related terms from this

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Internal paths in single or double quotes, written as "internal:node/99", for example, are replaced with the appropriate absolute URL or path. Paths to files in single or double quotes, written as "files:somefile.ext", for example, are replaced with the appropriate URL that can be used to download the file.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Syntax highlight code surrounded by the {syntaxhighlighter SPEC}...{/syntaxhighlighter} tags, where SPEC is a Syntaxhighlighter options string or "class="OPTIONS" title="the title".
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.