martin-evans.me.uk Always finish the day on a success

Just spent around an hour trying to get my wife's laptop to connect wirelessly to my Canon IP5000 printer connected to my new Windows 7 x64 machine. It all worked fine when I was running Windows XP x86.

In the last few days I've released what hopefully will be the last development release of DBD::ODBC (1.24_4). If you run Windows especially and Perl 5.13 even more, then please test.

Ok, so someone is bound to say I'm just using a blog entry to complain about a company and although I am, it was not me that got the bum end of a deal from Dell. My friend, does not use computers every day and is self employed in the building industry but needs better records for his tax and the production of bills and would like to watch a DVD or two. He found a laptop he liked but could not find anyone selling it and found something almost equivalent from Dell.

I just upgraded from Ubuntu 9.10 Karmic Koala to 10.04 Lucid and my Oracle SQL Developer stopped working entirely. I didn't bother trying to look in to it as my SQL Developer was rather old anyway so I downloaded 2.1.1.64 and it didn't work either. Seeing the warnings on the SQL Developer page about supported JDKs I first checked what I had installed.

I am happy to announce another development release of DBD::ODBC. Many thanks to everyone who has contributed to this release and especially to all my friends on the #dbi irc channel and perl monks. My intention is to add a lob writing method and full support for DBI's DiscardString and StrictlyTyped attributes in the next development release before releasing a final development release and finally a 1.25 full release. To support the new odbc_lob_read I've had to delay the binding of columns until the first fetch instead of as before when the result-set was described. This should not have any adverse effects but you are advised to test this release as without any feedback it will move to the next final release. The changes since the last full release are:

I currently maintain DBD:ODBC and needed to obtain a lob (large object) in chunks. It doesn't really matter why but in general the lob is very large and I can process it in chunks in my Perl code so it makes sense to read it in chunks instead of read it all in one go (thus requiring loads of memory). DBD::ODBC does not have this functionality currently.

In the last few days on and off I've been trying to locate a problem with a fairly complicated Perl daemon using POE which was taking a huge amount of time to return a large file via LWP::UserAgent. It's taken a while since in reality we were not doing a simple HTTP GET and the circumstances under which the problem occurs are difficult to set up. However, I've at last tracked it down to taint mode.

Not for the first time a Perl POE daemon in our development system seemed to be taking a long time on certain requests. It is a large amount of code and although we had our suspicions we've learnt the lesson now - Devel::NYTProf is so simple to use we had no hesitation in running it on this daemon. Instead of: you simply run: then a nytprof.out file is created and then you can generate the HTML report and view it with:

A great deal of issues arise in the dbi-users mailing list and to me personally concerning ODBC connection issues so I thought I'd describe the ODBC connection process here (with a slight Perl angle since I look after DBD::ODBC). The information here should be of general interest to anyone using ODBC.

I have uploaded the official 1.24 release of DBD::ODBC to CPAN. Many thanks to everyone who has helped with this whether it was patches or testing. Here are the changes since 1.23: =head2 Changes in DBD::ODBC 1.24 May 14, 2010 Minor change in Makefile.PL to only use NO_META if ExtUtils::MakeMaker is at least at version 6.10. Reported by Chunmei Wu. Minor change to test rt_50852 which had wrong skip count. =head2 Changes in DBD::ODBC 1.23_5 May 6, 2010 Added advice from Jan Dubois (ActiveState) on building DBD::ODBC for ActivePerl (see README.windows).