StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3465628
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2010-08-12T07:37:19.633
FavoriteCount
0
LastActivityDate
2010-08-12T08:05:36.210
LastEditDate
2010-08-12T08:05:36.210
LastEditorUserId
14860
OwnerUserId
14860
ParentId
3465580
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Well, actually: <pre><code>(A>=100 && (B<100 || B<A)) </code></pre> is the same as: <pre><code>(A>=100 && B<A) </code></pre> That's because, if <code>B < 100</code>, it's automatically less than <code>A</code> since <code>A >= 100</code> and here's the code that proves it (in C but C# should be the same): <pre><code>#include <stdio.h> static void test (int a, int b) { printf ("a=%3d, b=%3d : ok=%d\n", a, b, (a>=100 && (b<100 || b<a)) == (a>=100 && b<a)); } int arr[] = {1,2,3,99,100,101,199,200,201}; int main (void) { int i, j; for (i = 0; i < sizeof(arr)/sizeof(*arr); i++) { for (j = 0; j < sizeof(arr)/sizeof(*arr); j++) { test (arr[i], arr[j]); } } return 0; } </code></pre> It outputs: <pre><code>a= 1, b= 1 : ok=1 a= 1, b= 2 : ok=1 a= 1, b= 3 : ok=1 a= 1, b= 99 : ok=1 a= 1, b=100 : ok=1 a= 1, b=101 : ok=1 a= 1, b=199 : ok=1 a= 1, b=200 : ok=1 a= 1, b=201 : ok=1 a= 2, b= 1 : ok=1 a= 2, b= 2 : ok=1 a= 2, b= 3 : ok=1 a= 2, b= 99 : ok=1 a= 2, b=100 : ok=1 a= 2, b=101 : ok=1 a= 2, b=199 : ok=1 a= 2, b=200 : ok=1 a= 2, b=201 : ok=1 a= 3, b= 1 : ok=1 a= 3, b= 2 : ok=1 a= 3, b= 3 : ok=1 a= 3, b= 99 : ok=1 a= 3, b=100 : ok=1 a= 3, b=101 : ok=1 a= 3, b=199 : ok=1 a= 3, b=200 : ok=1 a= 3, b=201 : ok=1 a= 99, b= 1 : ok=1 a= 99, b= 2 : ok=1 a= 99, b= 3 : ok=1 a= 99, b= 99 : ok=1 a= 99, b=100 : ok=1 a= 99, b=101 : ok=1 a= 99, b=199 : ok=1 a= 99, b=200 : ok=1 a= 99, b=201 : ok=1 a=100, b= 1 : ok=1 a=100, b= 2 : ok=1 a=100, b= 3 : ok=1 a=100, b= 99 : ok=1 a=100, b=100 : ok=1 a=100, b=101 : ok=1 a=100, b=199 : ok=1 a=100, b=200 : ok=1 a=100, b=201 : ok=1 a=101, b= 1 : ok=1 a=101, b= 2 : ok=1 a=101, b= 3 : ok=1 a=101, b= 99 : ok=1 a=101, b=100 : ok=1 a=101, b=101 : ok=1 a=101, b=199 : ok=1 a=101, b=200 : ok=1 a=101, b=201 : ok=1 a=199, b= 1 : ok=1 a=199, b= 2 : ok=1 a=199, b= 3 : ok=1 a=199, b= 99 : ok=1 a=199, b=100 : ok=1 a=199, b=101 : ok=1 a=199, b=199 : ok=1 a=199, b=200 : ok=1 a=199, b=201 : ok=1 a=200, b= 1 : ok=1 a=200, b= 2 : ok=1 a=200, b= 3 : ok=1 a=200, b= 99 : ok=1 a=200, b=100 : ok=1 a=200, b=101 : ok=1 a=200, b=199 : ok=1 a=200, b=200 : ok=1 a=200, b=201 : ok=1 a=201, b= 1 : ok=1 a=201, b= 2 : ok=1 a=201, b= 3 : ok=1 a=201, b= 99 : ok=1 a=201, b=100 : ok=1 a=201, b=101 : ok=1 a=201, b=199 : ok=1 a=201, b=200 : ok=1 a=201, b=201 : ok=1 </code></pre> But, if those were just general items rather than specific ones, <code>&&</code> has a <a href="http://msdn.microsoft.com/en-us/library/aa691323%28VS.71%29.aspx" rel="nofollow noreferrer">higher precedence</a> than <code>||</code> in C#, so you should use: <pre><code>(A>=100 && (B<100 || B<A)) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLogical operators: (A>=100 && B<100 || B<A)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpaxdiablo
UserOwnerUserId
1. USpaxdiablo
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. 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
 VTUndeletion
CommentsPostId

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.