StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3358482
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2010-07-28T23:54:40.560
FavoriteCount
0
LastActivityDate
2010-07-30T13:33:10.670
LastEditDate
2010-07-30T13:33:10.670
LastEditorUserId
184908
OwnerUserId
184908
ParentId
3357675
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
The current REGEX <pre><code>/^[$]?(\d{0,3})[$]?[\.]?[\/]?[\s]?[\-]?(\d{3})[\s]?[\.]?[\/]?[\-]?(\d{4})[\s]?[x]?(\d*)$/ </code></pre> has a lot of issues, resulting in it matching all of the following, among others: <code>(0./ -000 ./-0000 x00000000000000000000000)</code> <code>()./1234567890123456789012345678901234567890</code> <code>\)\-555/1212 x</code> I think this REGEX is closer to what you're looking for: <pre><code>/^(?:(?:(?:1[.\/\s-]?)(?!$))?(?:\((?=\d{3}$))?((?(?!(37|96))[2-9][0-8][0-9](?<!(11)))?[2-9])(?:$(?<=\(\d{3}))?)?[.\/\s-]?([0-9]{2}(?<!(11)))[.\/\s-]?([0-9]{4}(?<!(555(01([0-9][0-9])|1212))))(?:[\s]*(?:(?:x|ext|extn|ex)[.:]*|extension[:]?)?[\s]*(\d+))?$/ </code></pre> or, exploded: <pre><code><? $pattern = '/^ # Matches from beginning of string (?: # Country / Area Code Wrapper [not captured] (?: # Country Code Wrapper [not captured] (?: # Country Code Inner Wrapper [not captured] 1 # 1 - CC for United States and Canada [.\/\s-]? # Character Class ('.', '/', '-' or whitespace) for allowed (optional, single) delimiter between Country Code and Area Code ) # End of Country Code (?!\() # Lookahead, only allowed if not followed by an open parenthesis )? # Country Code Optional (?: # Opening Parenthesis Wrapper [not captured] \( # Opening parenthesis (?=\d{3}$) # Lookahead, only allowed if followed by 3 digits and closing parenthesis [lookahead never captured] )? # Parentheses Optional ((?(?!(37|96))[2-9][0-8][0-9](?<!(11)))?[2-9]) # 3-digit NANPA-valid Area Code [captured] (?: # Closing Parenthesis Wrapper [not captured] \( # Closing parenthesis (?<=\(\d{3}) # Lookbehind, only allowed if preceded by 3 digits and opening parenthesis [lookbehind never captured] )? # Parentheses Optional )? # Country / Area Code Optional [.\/\s-]? # Character Class ('.', '/', '-' or whitespace) for allowed (optional, single) delimiter between Area Code and Central-office Code ([0-9]{2}(?<!(11))) # 3-digit NANPA-valid Central-office Code [captured] [.\/\s-]? # Character Class ('.', '/', '-' or whitespace) for allowed (optional, single) delimiter between Central-office Code and Subscriber number ([0-9]{4}(?<!(555(01([0-9][0-9])|1212)))) # 4-digit NANPA-valid Subscriber Number [captured] (?: # Extension Wrapper [not captured] [\s]* # Character Class for allowed delimiters (optional, multiple) between phone number and extension (?: # Wrapper for extension description text [not captured] (?:x|ext|extn|ex)[.:]* # Abbreviated extensions with character class for terminator (optional, multiple) [not captured] | # OR extension[:]? # The entire word extension with character class for optional terminator )? # Marker for Extension optional [\s]* # Character Class for allowed delimiters (optional, multiple) between extension description text and actual extension (\d+) # Extension [captured if present], required for extension wrapper to match )? # Entire extension optional $ # Matches to end of string /x'; // /x modifier allows the expanded and commented regex ?> </code></pre> This modification provides several improvements. <ol> <li>It creates a configurable group of items that can match as the extension. You can add additional delimiters for the extension. This was the original request. The extension also allows for a colon after the extension delimter.</li> <li>It converts the sequence of 4 optional delimiters (dot, whitespace, slash or hyphen) into a character class that matches only a single one.</li> <li>It groups items appropriately. In the given example, you can have the opening parentheses without an area code between them, and you can have the extension mark (space-x) without an extension. This alternate regular expression requires either a complete area code or none and either a complete extension or none.</li> <li>The 4 components of the number (area code, central office code, phone number and extension) are the back-referenced elements that feed into $matches in <code>preg_match()</code>.</li> <li>Uses lookahead/lookbehind to require matched parentheses in the area code.</li> <li>Allows for a 1- to be used before the number. (This assumes that all numbers are US or Canada numbers, which seems reasonable since the match is ultimately made against NANPA restrictions. Also disallows mixture of country code prefix and area code wrapped in parentheses.</li> <li>It merges in the NANPA rules to eliminate non-assignable telephone numbers. <ol> <li>It eliminates area codes in the form 0xx, 1xx 37x, 96x, x9x and x11 which are invalid NANPA area codes.</li> <li>It eliminates central office codes in the form 0xx and 1xx (invalid NANPA central office codes).</li> <li>It eliminates numbers with the form 555-01xx (non-assignable from NANPA).</li> </ol></li> </ol> It has a few minor limitations. They're probably unimportant, but are being noted here. <ol> <li>There is nothing in place to require that the same delimiter is used repeatedly, allowing for numbers like 800-555.1212, 800/555 1212, 800 555.1212 etc.</li> <li>There is nothing in place to restrict the delimiter after an area code with parentheses, allowing for numbers like (800)-555-1212 or (800)/5551212.</li> </ol> The NANPA rules are adapted from the following REGEX, found here: <a href="http://blogchuck.com/2010/01/php-regex-for-validating-phone-numbers/" rel="nofollow noreferrer">http://blogchuck.com/2010/01/php-regex-for-validating-phone-numbers/</a> <pre><code>/^(?:1)?(?(?!(37|96))[2-9][0-8][0-9](?<!(11)))?[2-9][0-9]{2}(?<!(11))[0-9]{4}(?<!(555(01([0-9][0-9])|1212)))$/ </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POValidating US phone number with php/regex
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USebynum
UserOwnerUserId
1. USebynum
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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.