If you are just using MySQL, then you can benefit from some special attributes in DBD::mysql, such as mysql_is_num.
For example:
$dbh->do(qq{DROP TABLE IF EXISTS test.test1}); $dbh->do(qq{CREATE TABLE test.test1( f_int int, f_char char(10), f_double double, f_bigint BIGINT, f_varchar VARCHAR(10), f_date DATE, f_timestamp timestamp )}); my $sth= $dbh->prepare(qq{SELECT * from test.test1}); $sth->execute() or die "execution error ($DBI::errstr)\n"; my @columns = @{$sth->{NAME}}; for (0 .. $#columns) { printf "%s %s numeric\n", $columns[$_], $sth->{mysql_is_num}[$_] ? "is" : "isn't"; } __END__ output: f_int is numeric f_char isn't numeric f_double is numeric f_bigint is numeric f_varchar isn't numeric f_date isn't numeric f_timestamp isn't numeric
HTH
In reply to Re: DBI scanning of column definitions
by rnahi
in thread DBI scanning of column definitions
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |