in reply to Data format verification for insertion into a database
I can't see any sense in rolling out a module which just consolidates various bits from other modules. It may make sense if you're doing this for some application (inlining only the patterns you're going to use from Regexp::Common for your app is a good idea), but as a module on cpan? Unless you're releasing that app on CPAN it doesn't make much sense to me.
I say you contact Abigail-II, the author of Regexp::Common and see if you can contribute.
Data::Verify 0.01.24 supports 25 types: BOOL - a true or false value CREDITCARD - is one of a set of creditcard type (DINERS, BANKCARD, VISA, .. DATE - a date DATETIME - a date and time combination EMAIL - an email address ENUM - a member of an enumeration GENDER - a gender (male|female) INT - an integer IP - an IP (V4, MAC) network address LONGTEXT - text with a max length of 4294967295 (2^32 - 1) characters (.. MEDIUMTEXT - text with a max length of 16777215 (2^24 - 1) characters (al.. NUM - a number QUOTED - a quoted string REAL - a real REF - a reference to a variable SET - a set (can have a maximum of 64 members (mysql)) TEXT - blob with a max length of 65535 (2^16 - 1) characters (alias.. TIME - a time TIMESTAMP - a timestamp TINYTEXT - text with a max length of 255 (2^8 - 1) characters (alias my.. URI - an http uri VARCHAR - a string with limited length of choice (default 60) WORD - a word (without spaces) YEAR - a year in 2- or 4-digit format YESNO - a simple answer (yes|no)
update: Perhaps roll out Regexp::Common::MySQL, which would pull out patterns from Regexp::Common::date and Regexp::Common::sql ... or something
|
MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy. |
|
|---|