StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18822080
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-16T07:00:12.377
FavoriteCount
0
LastActivityDate
2013-09-16T10:11:46.873
LastEditDate
2013-09-16T10:11:46.873
LastEditorUserId
1651840
OwnerUserId
1651840
ParentId
18821218
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You need a second schema to describe the Signature namespace. The following code build a simple example for a xml file based on two different namespaces. Here the second namespace schema ... <pre><code><?xml version="1.0" encoding="UTF-8"?>  <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://my.second.namespace" xmlns:tns="http://my.second.namespace" elementFormDefault="qualified"> <element name="SomethingElse" type="string"></element> </schema> </code></pre> The schema for the main namespace ... <pre><code><?xml version="1.0" encoding="UTF-8"?>  <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://my.first.namespace" xmlns:tns="http://my.first.namespace" xmlns:S="http://my.first.namespace" xmlns:T="http://my.second.namespace" elementFormDefault="qualified"> <import namespace="http://my.second.namespace" schemaLocation="./SecondNamespaceSchema.xsd"/> <element name="Root"> <complexType> <sequence> <element name="Head"> <complexType> <sequence> <element name="Something" type="string"></element> <element ref="T:SomethingElse"/> </sequence> </complexType> </element> <element name="Body" type="string"></element> </sequence> </complexType> </element> </schema> </code></pre> ... and a sample xml that puts all together. <pre><code><?xml version="1.0"?>  <S:Root xmlns:S="http://my.first.namespace" xmlns:T="http://my.second.namespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://my.first.namespace ./Sample.xsd"> <S:Head> <S:Something/> <T:SomethingElse/> </S:Head> <S:Body> </S:Body> </S:Root> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTwo different xmlns:xs in XML Schema
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USOkieOth
UserOwnerUserId
1. USOkieOth
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.