Martin has informed me that Microsoft doesn't support SQLDescribeParam and
in the absence of an explicit bind_param, miscasts the data as VARCHAR.
$sth->bind_param(1, undef, SQL_LONGVARBINARY);
Solved the problem.
ssistance would be much appreciated. (A similar inquiry has been posted
at http://perlmonks.org/?node_id=1153796)
--
Jerrad Pierce, Research Assistant 2, NMR Group
617-284-6230x21
ndef ) [1 items] at db_ODBC.pl line 69
3000400210004e04051482240724! ->
DESTROY for DBD::ODBC::db (DBI::db=HASH(0x25f2608)~INNER)
thr#679fb8SQLDisconnect=0
! <- DESTROY= ( undef ) [1 items] during global destruction
--
Jerrad Pierce, Research Assistant 2, NMR Group
617-284-6230x21
>$dbh->func([
> [ 'tableA', 'DBM', 'file1.dbm' ],
> [ 'tableB', 'DBM', 'file2.dbm' ],
> [ 'tableC', 'CSV', 'file3.csv' ],
>,'ad_catalog');
That would work too, I had assumed one handle per database/table/DBM
I suppose one could also provide another argument declaring what
My thoughts were the following:
table name in the statement is ignored, there is only one table per DBM.
this allows you to drop in a different DBD later
the column name is ignored, see above
For a second run:
multiple columns are allowed however, the relationship between the first
No word or progress? I independently arrived at the some conlusion myself,
but have yet to get around to doing it. Perhaps next week if you don't
know of any pre-existing work, a good intro to DBM.
