StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17715567
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-07-18T05:56:21.287
FavoriteCount
0
LastActivityDate
2013-07-18T06:04:18.303
LastEditDate
2013-07-18T06:04:18.303
LastEditorUserId
1093528
OwnerUserId
1093528
ParentId
17715388
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
If you have a limited sequence of characters following one another you can use a <code>Pattern</code>, <code>.find()</code> on a matcher on your input and just invert the test: <pre><code>// Only the alternation is needed, no need for the capture private static final Pattern PATTERN = Pattern.compile("012|123|234|345|456|567|678|789|890"); // ... if (PATTERN.matcher(input).find()) // fail: illegal sequence found </code></pre> But if you want to detect that code points follow one another you have to use character functions: <pre><code>final CharBuffer buf = CharBuffer.wrap(input); int maxSuccessive = 0; int successive = 0; char prev = buf.get(); char next; while (buf.hasRemaining()) { next = buf.get(); if (next - prev == 1) successive++; else { maxSuccessive = Math.max(maxSuccessive, successive); successive = 0; } prev = next; } // test maxSuccessive </code></pre> Note however that this will test successive characters according to "canonical ordering", not collation. In some locales, for instance, what is immediately after <code>a</code> is <code>A</code>, not <code>b</code>. <hr> More generally, if you want to test for password requirements and constraint evolves, you are better off splitting things a bit. For instance, consider this: <pre><code>public interface PasswordChecker { boolean isValid(final String passwd); } </code></pre> Implement this interface for each of your checks (for instance, length, presence/absence of certain characters, etc), and when you do check for a password, have a <code>List</code> of checkers; the password is invalid if one checker returns false: <pre><code>private final List<PasswordChecker> checkers = ...; // then for (final PasswordChecker checker: checkers) if (!checker.isValid(passwd)) return false; return true; </code></pre> If you use Guava, you can forget about <code>PasswordChecker</code> and use <code>Predicate<String></code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORegEx - Java - Matching Strings (012|123|234|345|456|567|678|789|890)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USfge
UserOwnerUserId
1. USfge
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORegEx - Java - Matching Strings (012|123|234|345|456|567|678|789|890)
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.