Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If your document is unicode, you only need to escape the same ones as for XML in your text <sup>[<a href="http://www.w3.org/TR/html4/intro/sgmltut.html#h-3.2.2" rel="noreferrer">spec</a>] [<a href="http://www.w3.org/International/questions/qa-escapes#use" rel="noreferrer">doc</a>]</sup>:</p> <pre class="lang-none prettyprint-override"><code>&amp; becomes &amp;amp; &lt; becomes &amp;lt; &gt; becomes &amp;gt; </code></pre> <p>In attribute values you must also escape the quote character <sup>[<a href="http://www.w3.org/TR/html4/charset.html#h-5.3.2" rel="noreferrer">spec</a>]</sup>:</p> <pre><code>" becomes &amp;quot; ' becomes &amp;#39; </code></pre> <p>If your document is ASCII or another non-Unicode encoding and you're using characters that aren't supported, you'll need to escape them. Otherwise, you're fine<sup>1</sup>.</p> <p>You usually do not want to escape spaces as <code>&amp;nbsp;</code>. <code>&amp;nbsp;</code> is not a normal space, it's a non-breaking space <sup>[<a href="http://en.wikipedia.org/wiki/Non-breaking_space" rel="noreferrer">wiki</a>]</sup>. You can use these instead of normal spaces to prevent a line break from being inserted between two words, or to insert&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;extra&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;space&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;without it being automatically collapsed, but you won't need to do this very often.</p> <hr> <p><sup>1</sup> You're fine, as long as you're inserting the escaped text somewhere that it makes sense to insert ordinary text (i.e. not inside a <code>&lt;style&gt;</code> or <code>&lt;script&gt;</code> tag, and not inside an attribute value). Otherwise you must take other precautions as mentioned in <a href="https://stackoverflow.com/a/7382443/1114">daxelrod's answer</a> and <a href="https://www.owasp.org/index.php/XSS_%28Cross_Site_Scripting%29_Prevention_Cheat_Sheet#XSS_Prevention_Rules" rel="noreferrer">described here by the Open Web Application Security Project</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhich characters need to be escaped on HTML?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJeremy
    1. USJeremy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhich characters need to be escaped on HTML?
      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. COCould you possibly cite some documentation for the statement that if the document is in unicode then you only need to escape the 5 XML character entities? I'm interested in learning more.
      singulars
      1. PO
      1. USMichael Waterfall
    2. CO@MichaelWaterfall: I can't find any documentation saying that specifically, but I added references to the HTML specification where it mentions which characters must be escaped in attributes and in text, and added a footnote clarifying what I mean by "escaped text". The only other reason you would need to use HTML entities is to represent characters that can't be represented by the character set you're using, but this can't occur with Unicode.
      singulars
      1. PO
      1. USJeremy
    3. COThe character `>` never needs to be escaped. The character `"` (respectively `'`) needs to be escaped only in the rare case where it appears inside an attribute value that has that same character as delimiter. Moreover, in HTML syntax (as opposite to XHTML), characters `&` and `<` need not always be escaped, see the specs for details.
      singulars
      1. PO
      1. USJukka K. Korpela
 

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