StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20366821
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-04T04:25:13.590
FavoriteCount
0
LastActivityDate
2013-12-04T04:25:13.590
LastEditDate
LastEditorUserId
0
OwnerUserId
1679310
ParentId
20357550
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
One way how to achieve this (one of many, because you can also use some fully-typed filter object etc or some query builder) could be like this draft: Part one and two: <pre><code>// I. a reference to our query var query = session.QueryOver<Event>(() => @eventAlias); // II. join, filter... whatever needed query .Fetch(@event => @event.FiscalYear).Eager var joinQuery = query .JoinQueryOver(...) .Where(() => !@eventAlias.IsDeleted) ... </code></pre> Part three: <pre><code>// III. Order BY // Assume we have a list of strings (passed from a UI client) // here represented by these two values var sortBy = new List<string> {"Name", "CodeDesc"}; // first, have a reference for the OrderBuilder IQueryOverOrderBuilder<Event, Event> order = null; // iterate the list foreach (var sortProperty in sortBy) { // use Desc or Asc? var useDesc = sortProperty.EndsWith("Desc"); // Clean the property name var name = useDesc ? sortProperty.Remove(sortProperty.Length - 4, 4) : sortProperty; // Build the ORDER order = order == null ? query.OrderBy(Projections.Property(name)) : query.ThenBy(Projections.Property(name)) ; // use DESC or ASC query = useDesc ? order.Desc : order.Asc; } </code></pre> Finally the results: <pre><code>// IV. back to query... call the DB and get the result IList<Event> s = query .List<Event>(); </code></pre> This draft is ready to do sorting on top of the root query. You can also extend that to be able to add some order statements to <code>joinQuery</code> (e.g. if the string is "FiscalYear.MonthDesc"). The logic would be similar, but built around the joinQuery (see at the part one)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POdynamic asc desc sort
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRadim Köhler
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POdynamic asc desc sort
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.