At one level, what constitutes correct format is application-specific.

At another level, things like data with embedded quotes can be handled automatically by DBI if you use parameter markers in your queries and pass values to execute(), where they'll be automagically quoted.

Could you be a little more specific about what you mean by "verification of data format"?

For instance: make certain that a date is in the proper sequence, make certain that something which is supposed to be an integer is most certainly an integer, etc. There are also other checks such as proper e-mail address formatting that I would like to see rolled up into one friendly module (outside of Email::Valid so I don't have to import 500 modules to know that my data is properly formatted). Hmmm..



antirice    
The first rule of Perl club is - use Perl
The ith rule of Perl club is - follow rule i - 1 for i > 1

There are also other checks such as proper e-mail address formatting that I would like to see rolled up into one friendly module ...

As of yet, there is no such friendly module, at least as far as I know (though perhaps someone else knows better). You'll need to build up the verification you need from individual pieces.

eval {
    local $dbh -> {RaiseError} = 1;
    local $dbh -> {PrintError} = 0;
    local $dbh -> {AutoCommit} = 0;

    my $sql = "INSERT INTO foo_table VALUES (?, ?)";
    my $sth = $dbh -> prepare ($sql);
    $sth -> execute ($key, $date);
};
if ($@) {
    # Some error occurred, for instance due to wrong dateformat.
    $dbh -> rollback;
    # Inspect $@ for error, take appropriate action.
    ...
}
else {
    $dbh -> commit;
}
[download]

Abigail

• Data::FormValidator
• Params::Validate
• Data::Types
• Data::Verify

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.

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.

sample usage (readmore for code)

user[29]~/bin>mysql-date-fixer next tuesday
2003-04-29 01:06:55
user[30]~/bin>mysql-date-fixer Jan 1 2021
2021-01-01 00:00:00
user[31]~/bin>mysql-date-fixer 982321156
2001-02-16 03:59:16
[download]

if (data_submitted()) {
    @errors = validate_data();
    if (@errors) {
        output_errors(@errors);
        output_form();
    }
    else {
        process_data();
    }
}
else {
    output_form();
}
[download]

Forms appearence, data validation and processing are VERY application specific, so I don't think that you might cheat a lot there. On the other hand, the validate_data() sub can win a lot from simplified validations. I'd say that it would be very helpful if I could do something like this (pseudo-code again):

push @errors, "Age not in range" if (!is_integer($age,5,100));
push @errors, "Ugly date format" if (!is_date($date,"YYYY-MM-DD"));
push @errors, "Unknown image type" if (!is_file_type($uploaded_file, "
+image/jpeg"));
[download]

Leonid Mamtchenkov