Fun getting DBI/DBD::ODBC working on a 64bit Windows machine

Firstly, I should say I don't use Windows that much these days. The Windows machines where I test DBI and DBD::ODBC I set up ages ago with a Perl built with MS Developer Studio and I tend to keep them for that purpose. However, I bought a whole load of nice shiny new parts to build myself a new PC a month ago and installed Ubuntu and Windows as I thought I could get a more up to date Perl on Windows at home.

DBD::ODBC 1.25 release

I'm pleased to announce the 1.25 release of DBD::ODBC. A full list of changes since the last major release is listed below and at DBD::ODBC Changes. New features include support for MS SQL Server's XML type, a new odbc_lob_read method, overriding of types on bind_col. Many thanks to everyone who has reported issues and helped with the development and testing of DBD::ODBC and especially all my friends on #dbi, Perl Monks and my colleagues at Easysoft Limited..

Why doesn't length() on DBI/DBD::ODBC returned unicode data return the correct length in characters?

Today someone posted a problem using the SQL Server XML datatype with DBI/DBD::ODBC on the dbi-users mailing list. I sorted their problem pretty quickly but noticed his code using length() on scalars which were bound with bound_col was not reporting the correct length. The example and output are below:

Installing Canon X86 printer drivers on Windows 7 x64

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.

Last DBD::ODBC 1.24 development release before official 1.25 - please test

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.

Buy a new Dell laptop and you too could get this support

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.

Upgrade to Ubuntu 10.04 broke my Oracle SQL Developer

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.

New 1.24_2 development release of DBD::ODBC

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:

character|binary lob reading in DBD::ODBC

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.

Why is taint mode so slow?

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.

Syndicate content