Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would personally go with option 1, You mention two additional tables later so I assume you're thinking of.</p> <pre><code>Table -Tag Fields - TagID, TagName Table -TagArticle Fields - ArticleID, TagID Table - Article Fields - ArticleID, blah, blah, blah </code></pre> <p>This shouldn't require much more in the way of storage than dumping to a field in Article. Plus it is normalised which will always stand you in good stead for the future and will leave your database far better able to search for articles by tag. As for updating, chances are you'll only be updating occasionally compared to the number of times you're reading so the impact should be negligible and I cant think of any maintenance tasks beyond ensuring your indices are up to date which you're going to have to do on other tables anyway and should be automated.</p> <p>Fringe benefits mean you can quickly create things like a top tags list or a tag cloud.</p>
    singulars
    1. This table or related slice is empty.
    1. POBest Way to Implement Tags (Similar to StackOverflow)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRobb
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBest Way to Implement Tags (Similar to StackOverflow)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWell, I would expect it to require more storage for the additional tables and relationships, but perhaps it would be sufficiently offset by not having to repeat the tag words themselves. My actual case may even be a bit more complex. For example, I may have different kinds of tags link platforms, language, libraries, etc. I'm not sure, but this approach should work fine for that too. Thanks.
      singulars
      1. PO
      1. USJonathan Wood
    2. CO@Jonathan Wood - I'm not certain on the overheads for a table however if you use an int for the ID's that's 4 bytes per int so tagarticle contains 8 bytes per line, varchars are 1 byte per character + 2 bytes overhead. Taking the 3 tags on your question my table requires 24 bytes, storing them in a textfield (assuming you use a 1 char delimiter) requires 30 bytes, 2 indices on the tag article columns would likely cancel out against your full text index for searching the tag field.
      singulars
      1. PO
      1. USRobb
    3. COWell, in addition to the table itself, you'd also have the indexes. But I'm actually more concerned about overhead required to maintain the data. In a text field, you just save the data the user entered. Using multiple tables, you'd have to do several checks on the database: is this tag already defined--create if not, is this article already associated with this tag--create if not. And similar steps to remove a tag. For a db connected to the web, it certainly represents additional workload. That said, I'm still leaning to the approach you suggested. Just wondering about the effects.
      singulars
      1. PO
      1. USJonathan Wood
 

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