Limitation of fetchrow_hashref with DBD::ODBC

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Chase Putans - 01 Jul 2009 18:47 GMT

I am doing a prepare/execute/fetchrow_hashref and for columns that have
names longer than 30 characters, the hash key is truncated to the first
30. Is this a known issue, and if so, is there a workaround for it? I
am using unixODBC 2.2.11 and and DBD::ODBC 1.17 (also tried this with
1.22).

Thanks.

Reply to this Message

Martin Evans - 02 Jul 2009 11:46 GMT

> I am doing a prepare/execute/fetchrow_hashref and for columns that have
> names longer than 30 characters, the hash key is truncated to the first
[quoted text clipped - 5 lines]
>
> Thanks.

I believe it is down to what the driver returns as
SQL_MAX_COLUMN_NAME_LEN (at least it is in recentish DBD::ODBCs).

If you turn on tracing in DBD::ODBC at level 15 and search the output
for MAX_COLUMN_NAME_LEN it should say what it found (certainly in 1.22 -
not sure about 1.17).

Martin

Signature

Martin J. Evans
Easysoft Limited
http://www.easysoft.com

Reply to this Message

Webmaster Forum / Perl / DBI Library / July 2009

Limitation of fetchrow_hashref with DBD::ODBC