Hi Reinhard,
last week I've been away from office, therefore I didn't answer your email
up til now.
I really doubt being able to help a lot with your actual question.
Theoretical you should be able to work from windows against DB2 on all
different platforms in the same way.
But talking about
Hi Manfred,
Manfred Beilfuss wrote:
Hi Reinhard,
last week I've been away from office, therefore I didn't answer your email
up til now.
I know it, it is no problem for me.
I really doubt being able to help a lot with your actual question.
Theoretical you should be able to work from
Hi Reinhard,
I really don't know why your blob's are splitted on OS/390 nor can I judge,
if and when or where they need to get splitted.
In my last firm, we did a project with db2/V6 on both winnt and OS390 and
we did load blob's greater than 2 MB down from OS390 to clients on NT.
But I don't
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.89.tar.gz
size: 42988 bytes
md5: cde236e5d51ee4097cb0336874851c0f
Changes:
Added an alternative implementation for type_info_all(), which is
enabled if $dbh-{ado_ti_ver} == 2.
!!! The next release of DBD::ADO may default to this new
From: Tim Bunce [mailto:[EMAIL PROTECTED]
But the Issuing rollback() warning is now only generated if AutoCommit
is turned off and Executed is true.
I'll miss the warning. It was an easy way to know I or my programmers were being
sloppy with explicit disconnects.
Enterprise wide all our
On Mon, Feb 16, 2004 at 03:46:28PM -0600, Jay Hannah wrote:
I would *love* to set another flag/whatever so DBI would bark at us
whenever $dbh's were garbage collected. Then we'd explicitly know to
slap ourselves for writing sloppy code... With the warning gone I fear
we won't know we're being
From: Andrew Pimlott [mailto:[EMAIL PROTECTED]
On Mon, Feb 16, 2004 at 03:46:28PM -0600, Jay Hannah wrote:
I would *love* to set another flag/whatever so DBI would bark at us
whenever $dbh's were garbage collected.
Can I ask exactly what you are worried about?
...
Or am I missing some
