On Tue, 14 Dec 2004 16:47:39 +0000, Tim Bunce <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 14, 2004 at 07:08:08AM -0800, Jonathan Leffler wrote:
> > I had certainly managed to miss this change - which could easily
> > account for some of the weirdnesses I'd been seeing in DBD::Informix.
> > (I haven't had a chance to do a thing for a week and more.)  This sort
> > of backwards incompatible change (in the use of set_err()) stuff needs
> > to be firmly highlighted.  I hope it was and I simply missed it.  I
> > would have put in place a comment about legacy drivers no longer being
> > good exemplars.
> 
> I don't think the change is backwards incompatible. It's a change
> in 'best practice' that ensures that errors on one db handle don't
> also appear on other children of the same handle.

OK - well, I've removed the Err, Errstr, State parameters from the
calls to _new_drh and _new_dbh and things seem to be working better
for me in DBD::Informix..

I'm now trying to work out how the DBIh_SET_ERR_SV() and - more
particularly - DBIh_SET_ERR_CHAR() functions can be used.  I've
spotted the section of DBI::DBD that discusses these - and I note that
it deprecates the use 'dbis' and 'DBIS' shortly afterwards.

I have a pair of central error reporting functions - for $drh and $dbh
as it happens - but they get passed only the imp_drh_t or imp_dbh_t
pointers and not an associated SV.  Is there a way to get back to the
SV from the imp_d?h_t pointer?

There are two problems I'm having.  One: what is the significance of
the SV *h and the imp_xxh_t * arguments?  Why are both needed; what
should those values be.

The other problem may be indirectly related.  DBD::Informix has some
(debugging) functions which I want to invoke from code that is
unrelated to Perl - and therefore should not be contaminated with Perl
nasties like SV pointers.  At the moment, that code is using DBIS to
find the debug level.  The code does not have 'h' or 'imp_xxh' values
available to it -- so it uses the DBIS to obtain the information it
needs.  Am I seeking to do the impossible (and if so, why does it have
to be impossible)?  ISTR that when I was first working with
DBD::Informix (1996 or so) I got fed up with all the SV/imp_??h_t
pointer pairs in the function calls when they weren't really both
necessary.  It may be that was more misguided than I knew, though it's
worked fine for a long time.

Yes, I know I'm trying to do too much with too little real knowledge
of what's going on.

> Having said that, there is certainly a possibility that changes
> in this area could be related to the 'weirdnesses' you're seeing.
> But that wouldn't be by design.
> 
> Tim.
> 
> > On Tue, 14 Dec 2004 10:12:54 +0100, Steffen Goeldner <[EMAIL PROTECTED]> 
> > wrote:
> > > DBI 1.31 suggests that lexically scoped variables should
> > > be passed to _new_dbh():
> > >
> > >    
> > > <http://search.cpan.org/~timb/DBI/Changes#Changes_in_DBI_1.31,_29th_November_2002>
> > >
> > > DBI 1.33 suggests that drivers should no longer pass these
> > > variables to _new_drh() or _new_dbh():
> > >
> > >    
> > > <http://search.cpan.org/~timb/DBI/Changes#Changes_in_DBI_1.33,_27th_February_2003>
> > >
> > > This leaves set_err() as the sole interface to set error
> > > codes.
> > >
> > > But "The Perl DBI Database Driver Writer's Guide" still
> > > suggests that global $err/$errstr/$state variables are
> > > needed for DBI:
> > >
> > >    <http://search.cpan.org/~timb/DBI-1.46/lib/DBI/DBD.pm#The_header>
> > >
> > > IMO, we can discard the paragraph without substitution.



-- 
Jonathan Leffler <[EMAIL PROTECTED]>  #include <disclaimer.h>
Guardian of DBD::Informix - v2
003.04 - http://dbi.perl.org
"I don't suffer from insanity - I enjoy every minute of it."

Reply via email to