I am not sure agree. Companies that don't upgrade DBI releases are
unlikely to upgrade DBD drivers more frequently; and they're always free
to use older DBD releases. We don't want to hold developers hostage to
the tendency of a few companies to be slow in upgrades.
At my workplace, a large
:$dsn, $userid, $password,
{ 'db2_application_name' = $name });
Cheers,
Hildo Biersma
*** dbdimp.c.orig Tue Dec 30 10:03:29 2008
--- dbdimp.cTue Dec 30 10:02:58 2008
***
*** 417,422
--- 417,440
if( SQL_SUCCESS != ret
be
reported as informational events instead.
I hope IBM gets around to including this (or an improved version) in the
next DBD::DB2 release; in the meantime, other users of DBD::DB2 may
benefit from this change.
Cheers,
Hildo Biersma
*** dbdimp.c.orig Tue Dec 30 10:03:29 2008
--- dbdimp.c
I'm not sure this is the same thing.
Both DB2 and Oracle support array inserts and array updates, where
an insert or update statement is executed with a list of values - i.e.
it is a more efficient way of executing the same insert/update multiple
times with a different list of values every
All,
We're trying to override the DBI-connect() method for DBD::DB2 to
support longer database names.
Some background:
- DB2 supports only 8-character database names and aliases
- We plan to have hundreds to thousands of them, so we end up with
non-intelligeble names.
- We have a mapping file
