Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There IS some way to separate the data from the presentation. You keep them separate! If you want to do some formatting on that text that you pulled from the database, go ahead and do that in your application code. Note that structural markup is an entirely different topic from presentation markup (font, color, layout, etc)</p> <p><a href="http://en.wikipedia.org/wiki/Separation_of_presentation_and_content" rel="nofollow">http://en.wikipedia.org/wiki/Separation_of_presentation_and_content</a> talks about this very point and makes a clear separation between presentation markup and structural markup in the paragraph under Intended Meaning.</p> <p>Storing formatting tags in your data generally points to poor separation between the two layers or a data model that isn't sufficient to represent your data properly. As the author is storing data in a database, that might indicate that he has just a single field for holding the "content block" of an article rather than multiple fields for the author, title, body, references, etc. For user input data, we often fall back to a markup inside the user content for designating structure. That happens through "fake" html tags or even real html/xml tags like <code>&lt;h1&gt;</code>, <code>&lt;em&gt;</code>, <code>&lt;a&gt;</code>, etc. </p> <p>Note that I'm not objecting to structural markup on principle but I would look carefully at why it's required if you're storing it in a database. I am objecting to presentation markup on principle.</p>
    singulars
    1. This table or related slice is empty.
    1. POHTML tags in database bad practice or good practice?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USgfortune
    1. USgfortune
    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. 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
    1. COShould i be **punished** for not _separating_ the `data` from the `presentation` in this comment?
      singulars
      1. PO
      1. USpenartur
    2. COCute. Just so someone doesn't read this and get confused thinking you were actually serious... The major difference between the author's question and this comment is that the author has the control necessary to separate the data from presentation. It may require restructuring the data model slightly to make the type of data easier to distinguish (markup indicating structure is common as is breaking data into multiple fields based on purpose) while you do not have the ability to do so in the comment. Though, note that `structural` markup is NOT presentation.
      singulars
      1. PO
      1. USgfortune
    3. COThe OP wanted to change the color of some part of the text; IMHO this is clearly the markup.
      singulars
      1. PO
      1. USpenartur
 

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