Comments
Sort by recent activity
Would be nice if regexes could be set to ignore white space so I could break complex ones into multiple lines and add comments
This is the regex I use to get a good mix of emails
((($[forename][._]?)?$[surname]|$[forename]([._]?$[surname])?)([0-9]{0,3})?|[a-z]{4,8}([0-9]{0,3}|\.[a-z]{4,10}))@example.com
Would be nicer if it were wrote
(
(?# Generate forname/surname pairs with a possible separator )
(
(?# optional forename, optional surname )
($[forename][._]?)?$[surname]
(?# non-optional forename, optional surname )
|$[forename]([._]?$[surname])?
)([0-9]{0,3})? (?# Sometimes add a numerix suffix to the forename/surname pair )
(?# Throw a few random ones into the mix )
|[a-z]{4,8}([0-9]{0,3}|\.[a-z]{4,10})
)@example.com
/ comments
Would be nice if regexes could be set to ignore white space so I could break complex ones into multiple lines and add comments
This is the regex I use to get a good mix of emails
((($&#...
I try to avoid using null in the database for text based columns preferring to use a blank string instead so an "Allow blank values" option for char, nchar, varchar and nvarchar types would be useful.
This would work in the same way as the "Allow null values" option.
Also when generating emails addresses, would be nice to be able to use the permutations of the generated forename / surname columns. / comments
I try to avoid using null in the database for text based columns preferring to use a blank string instead so an "Allow blank values" option for char, nchar, varchar and nvarchar types would be usef...