Let's say a phone number is valid in case it has 11 digits only (13 in case of using 00 instead of +). Separators could be anywhere. Take the valid numbers and bring to common format. Original idea was deleting all non-digits but using look-ahead made impossible to use + for remove non-digits, it ne...

Let's say a phone number is valid in case it has 11 digits (or 13 in case we use 00 instead of + ). Take those lines to common format. original idea was to remove all non-digit characters from those lines with simple match like but combined with look-ahead it just did not work, had to go through ea...

insert into table ( a, b, c ) values ( " insert into values (1,2,3)",1,2.3,"a,b" ); insert into table (ee,bb,cc) values (aa,234,"asj",2.3);

insert into (a,b,c) values (1,2.3,"test");

insert[\s]+into[\s]+\([\s](?.?)[\s]\)[\s]+values[\s]+\((?.?)[\s]*\);

Based on http://www.regular-expressions.info/creditcard.html This example includes test strings. This only validates the pattern, and not whether the credit card number passes a checksum validation. See the Luhn algorithm for details https://en.wikipedia.org/wiki/Luhn_algorithm...

regexp for year filtering

Extract jsfiddle links

this is the most perfect pattern I reach for url with query or anchor

Find single digits that are not part of an integer. For example, "27" should not match, but "27.1" will match the "1". "27.11" won't match.

Local variable and function parameter names should comply with a naming convention

Nickname validation. Only: letters _ One line. Tested with RoR

This expression converts any 3- or 4 digit timevalue to a value with colon between hours and minutes. So 345 is converted to 3:45 and 1500 is converted to 15:00