StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhy would I choose XSLT or XQuery over the other for html document generation?
primarykey
Id
1907907
data
AcceptedAnswerId
1908733
AnswerCount
4
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-12-15T14:41:46.550
FavoriteCount
1
LastActivityDate
2010-01-20T00:36:37.940
LastEditDate
LastEditorUserId
0
OwnerUserId
37055
ParentId
0
PostTypeId
1
Score
2
ViewCount
1012
LastEditorDisplayName
text
Body
I was researching alternatives to using Microsoft's <code>XslCompiledTransform</code> and everything seemed to point towards Saxon primarily and secondly XQSharp. As I started to look at documentation for Saxon I saw that XQuery could do the equivalent of my XSLTs that are no where near as terse as XQuery's markup is. What advantages do XSLTs offer over XQuery to deserve the much more detailed syntax? Would it be the templating functionality that can be created?
Tags
<c#><xslt><xquery><saxon>
Title
Why would I choose XSLT or XQuery over the other for html document generation?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USChris Marisic
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWhy would I choose XSLT or XQuery over the other for html document generation?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhy would I choose XSLT or XQuery over the other for html document generation?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POWhy would I choose XSLT or XQuery over the other for html document generation?
 UserUserId
 USJonathan
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. COWhy are you researching alternatives? What is it that is wrong with XslCompiledTransform that you have an issue with? Without that
 singulars
 PostPostId
 POWhy would I choose XSLT or XQuery over the other for html document generation?
 UserUserId
 USMurph
2. COMicrosoft's tool will fail on many valid XSL inputs, try transforming a document with querystrings in it that need &s...
 singulars
 PostPostId
 POWhy would I choose XSLT or XQuery over the other for html document generation?
 UserUserId
 USChris Marisic

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.