DBD_ODBC 1.21 does not accept DBI::SQL_LONGVARCHAR as data type anymore?

taioba has asked for the wisdom of the Perl Monks concerning the following question:

Hello, Monks. Like many I have struggled with trying to insert data in Access memo fields using DBI. Some of you have kindly explained how to do that in the posting below:

http://www.perlmonks.org/?node=Cannot%20insert%20into%20MS%20Access%20Memo%20field%20with%20DBI

I used to be able to insert info in memo fields in my Access database by binding the data using DBI::SQL_LONGVARCHAR. However, every since I upgraded DBD-ODBC to version 1.21, everytime I try to do that I get:

DBD::ODBC::st bind_param failed: Microsoft ODBC Microsoft Access Driver Invalid precision value (SQL-HY104)

If I use the column_info method to get the data type of the memo field, I get LONGCHAR instead of LONGVARCHAR. That does not work either, and I get the same message. Interesting enough, I do not have this problem if the data been inserted is smaller than 255 characters, even if it is a memo field. I also can insert data without a problem in INTEGER or VARCHAR fields. Any ideas?

Thanks for your ever wise and kind guidance.

Comment on DBD_ODBC 1.21 does not accept DBI::SQL_LONGVARCHAR as data type anymore?

Replies are listed 'Best First'.
Re: DBD_ODBC 1.21 does not accept DBI::SQL_LONGVARCHAR as data type anymore? by mje (Curate) on Jun 01, 2009 at 10:22 UTC
Create a self-contained small example in perl and post on rt.cpan.org under DBD::ODBC and I will look into it.	[reply]
Re^2: DBD_ODBC 1.21 does not accept DBI::SQL_LONGVARCHAR as data type anymore? by mje (Curate) on Jun 02, 2009 at 08:24 UTC
For anyone following this the rt is https://rt.cpan.org/Public/Bug/Display.html?id=46597.	[reply]
Re^3: DBD_ODBC 1.21 does not accept DBI::SQL_LONGVARCHAR as data type anymore? by mje (Curate) on Jun 02, 2009 at 16:02 UTC
This is technically a bug in DBD::ODBC since it does not follow the DBI specification in making parameter types sticky. However, an easy workaround for now is simply to leave the binding in the code but remove the data from the execute call. A proper fix is available in DBD::ODBC 1.21_1 which will appear on CPAN shortly.	[reply]
Re: DBD_ODBC 1.21 does not accept DBI::SQL_LONGVARCHAR as data type anymore? by Anonymous Monk on Jun 01, 2009 at 09:06 UTC
Downgrade? Try Re: Accessing MS-Access memofield via DBI	[reply]
Re^2: DBD_ODBC 1.21 does not accept DBI::SQL_LONGVARCHAR as data type anymore? by taioba (Acolyte) on Jun 01, 2009 at 16:52 UTC
If I downgrade to the previous version, I get this "Out of memory" error when trying to query the database. Upgrading fixed this problem, but created a new one. I am familiar with that posting, I have a couple of scripts running that used to work along those lines until I upgraded DBD-ODBC.	[reply]
Re^3: DBD_ODBC 1.21 does not accept DBI::SQL_LONGVARCHAR as data type anymore? by mje (Curate) on Jun 01, 2009 at 19:59 UTC
The out of memory error is known and fixed in 1.21 but you seem to have another issue. There is a report on rt.cpan.org now (perhaps that was you) and I will look into it tomorrow. Watch the rt and I'll post back here once I've looked at it.	[reply]