It appears that DBD::Oracle restricts the RowCacheSize to 128, why? I know how much memory I can afford to use for retrieving rows better than DBD::Oracle and as far as I can see this could be set a lot higher.
Another frustrating day with my broadband connection - thank you Virgin Media - not!
Ok, I'm new to drupal but I set up an email action to email me and associated it with a new comment. Then I added a comment as someone else and no email arrived. Then I found Using Drupal's email address in the mail.inc main function with -f which seemed to suggest the from address must be set if you are on fasthosts. Anyway the patch provided to mail.inc worked just fine. I include it here, partly as a reminder to me that I made this change:
Just spent a few hours trying to find out why the RowCacheSize attribute in DBD::Oracle does not seem to have any affect at all. The following code demonstrates the problem:
I frequent perl monks a bit and late yesterday an issue came in with DBD::ODBC and Microsoft Access. The perl monks node and rt 46597 detail it all quite well. It appears DBD::ODBC was not following the DBI specification (as it was originally written) to the letter with respect to sticky bound parameter types but since then Tim Bunce has modified the DBI pod slightly to allow DBDs to enable a bound parameter to be rebound with a different type. The change to DBD::ODBC was fairly small but by the time I'd added a test case, bumped the version to 1.21_1 and tested a dozen or so ODBC drivers this consumed a fair amount of time.