Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>To prevent Visual Studio incorrectly warning you that the <code>"Element 'legend' occurs too few times"</code> you need to correct Visual Studio's HTML and XHTML validation files.</p> <p>VS will then treat the <code>&lt;legend&gt;</code> tag as optional inside a <code>&lt;fieldset&gt;</code> tag (as per the spec).</p> <p>To do so, there are two files you need to edit: <code>html_5.xsd</code> and <code>xhtml_5.xsd</code>. For VS2010 these are found in (e.g.):</p> <p><code>C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Packages\schemas\html\</code></p> <p>Steps to take:</p> <ol> <li><p>Close Visual Studio</p></li> <li><p>Using a text editor open the file <code>html_5.xsd</code> found in the folder above.</p></li> <li><p>Locate the following line:</p> <p><em>(note there are two lines which are similar, the first is correct, the second needs editing)</em>:</p> <blockquote> <p><code>&lt;xsd:element name="legend" type="legendType" minOccurs="1" maxOccurs="1" /&gt;</code></p> </blockquote></li> <li><p>Edit the line to read:</p> <blockquote> <p><code>&lt;xsd:element name="legend" type="legendType" minOccurs="0" maxOccurs="1" /&gt;</code></p> </blockquote></li> <li><p>Save the file</p></li> <li><p>Repeat the process for the file <code>xhtml_5.xsd</code> which is in the same folder</p></li> </ol> <p>Now start Visual Studio and view your HTML5 file - the warning will be gone.</p> <p>I hope that helps others, and I hope the .xsd files will be corrected in a future update.</p> <p><strong>UPDATE:</strong></p> <p>The line you need to find may be:</p> <blockquote> <p><code>&lt;xsd:element ref="legend" minOccurs="1" maxOccurs="1" vs:firstchild="true"/&gt;</code></p> </blockquote> <p>If so, change the <code>minOccurs="1"</code> attribute to <code>minOccurs="0"</code></p>
    singulars
    1. This table or related slice is empty.
    1. POHTML5 Element 'legend' occurs too few times
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChris
    1. USChris
    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. VTDownMod
    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. COWhy the down vote...?! At least add a comment if you're going to downvote.
      singulars
      1. PO
      1. USChris
    2. CO+1. As you stated correctly that the `legend` is optional and that Visual Studio is reporting it incorrectly. I know the accepted answer worked around Visual Studio's issue by simply adding a legend but in the end, why add an optional element you don't need? In that case I think the correct solution is to ignore the VS warning as it is incorrect or as you stated, "fix" VS. I do not know why someone would have downvoted this.
      singulars
      1. PO
      1. USNope
    3. CO+1 for showing how to fix Visual Studio. The line I had to change was slightly different: <xsd:element ref="legend" minOccurs="0" maxOccurs="1" vs:firstchild="true" />
      singulars
      1. PO
      1. UStie
 

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