On Mon, Sep 18, 2006 at 10:30:49PM -0400, Sam Tregar wrote:
On Mon, 18 Sep 2006, Tim Bunce wrote:
Yes, and the same applies to AutoCommit. Whether it's a good thing or
not is debatable but it's been that way forever. The 'workaround' is
to explicitly state the attributes you want.
Hmmm,
Just finished a rather irritating debugging session trying to track
down a warning triggered by DBIx::Timeout. Turns out this code
doesn't exactly do what I mean:
$dbh-{PrintError} = 0;
Looks like it turns PrintError off, huh? Actually, as far as I can
tell it turns it on. The relevent C
On Mon, 18 Sep 2006, Sam Tregar wrote:
Looks like it turns PrintError off, huh? Actually, as far as I can
tell it turns it on. The relevent C code is (from dbih_set_attr_k):
else if (strEQ(key, PrintError)) {
DBIc_set(imp_xxh,DBIcf_PrintError, on);
Sheesh, ignore me. I see that's
On Mon, 18 Sep 2006, Sam Tregar wrote:
On Mon, 18 Sep 2006, Sam Tregar wrote:
Looks like it turns PrintError off, huh? Actually, as far as I can
tell it turns it on. The relevent C code is (from dbih_set_attr_k):
else if (strEQ(key, PrintError)) {
DBIc_set(imp_xxh,DBIcf_PrintError,
On Mon, Sep 18, 2006 at 05:05:52PM -0400, Sam Tregar wrote:
On Mon, 18 Sep 2006, Sam Tregar wrote:
On Mon, 18 Sep 2006, Sam Tregar wrote:
Looks like it turns PrintError off, huh? Actually, as far as I can
tell it turns it on. The relevent C code is (from dbih_set_attr_k):
else if
On Mon, 18 Sep 2006, Tim Bunce wrote:
Yes, and the same applies to AutoCommit. Whether it's a good thing or
not is debatable but it's been that way forever. The 'workaround' is
to explicitly state the attributes you want.
Hmmm, interesting. What would you think about making PrintError
