Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Store everthing in one big text field as Alex suggested. For searching, don't hammer your database, use <a href="http://lucene.apache.org/java/docs/" rel="noreferrer">Lucene</a>, or <a href="http://www.htdig.org/" rel="noreferrer">htdig</a> to create an index of your output. This way searches are very fast. The side effect is you make your searches a little more search engine friendly; you take your keywords field (as backslash suggested) and stick them in the meta-keywords attribute.</p> <p><b>Edit</b></p> <p>Unless you are only searching keywords, having the db do the searches will be horribly slow (ever searched a forum and it takes FOREVER?). There is no way for the database to index a </p> <pre><code> select.. where FULLTEXTFIELD like '%cookies%'. </code></pre> <p>It is frustrating looking for an article and the search doesn't return the results your are looking for because they weren't in the keyword field! Htdig allows you to search the full text of the article efficiently. Your searches will come back instantly, and EVERY term in the article is fully searchable. Putting the keywords in the meta tags will make searches on those terms come higher on the results page.</p> <p>Another benefit is fuzzy matching. If you search for 'activate' htdigg will match pages that have active, activation, activity etc. (configurable). Or if the user misspells a word, it will still be matched. You want your users to have a Google like experience, not an annoying one. :)</p> <p>You do need a script to create a list of links to all your pages from your database. Have htdig crawl this automatically and you never have to think about it again. </p> <p>Also htdig will crawl your non database pages as well so your whole site is searchable through the same simple interface.</p> <p>As for the keyword field , you <i>should</i> have a separate table called keywords with the id of the article and a keyword field (1 keyword per row). But for simplicity, having a single field in the db isn't a terrible idea, it makes updating the keywords pretty easy if you put it in a form.</p> <p>If you don't want to fuss with all the hassle of that, you can try using <a href="http://www.google.com/cse" rel="noreferrer">Google custom search</a>. it is far less work, but you have no guarantee that all your pages will get indexed.</p> <p>Good luck!</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to store articles or other large texts in a database
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USByron Whitlock
    1. USByron Whitlock
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to store articles or other large texts in a database
      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. VTAcceptedByOriginator
    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. COWow, thank you Byron. Your edit was a big help and ht://Dig doesn't seem quite as restrictive as I thought. For a really small site having the DB do the search isn't a huge deal I am sure, but I am hoping if my project works for my site I can reuse it for others and it would be nice if it was scalable. But that's for the future, for the present I need to actually code the thing :)
      singulars
      1. PO
      1. USEtzeitet
 

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