On Fri, 05 Dec 2008 14:46:10 +0000, Martin Evans
<[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Merijn and I have implimented it in DBD::Oracle and DBD::Unify
> > respectifully. I amd about to review the thread and see if I have to
> > manke any futher changes to DBD::Oracle.
> >
> > It think the key is gettin Tim B on board.
> >
> > I myself have fount it a great help when debugging as most of bugs that
> > come up with DBD::Oracle have to do with OCI nd not DBI.
> >
> > Just my 2c for today
> >
> > Cheers
> > John SColes
>
> Yes I saw the changes to Unify and Oracle but Unify included stuff like:
>
> sub parse_trace_flag
> {
> my ($dbh, $name) = @_;
> return 0x7FFFFF00 if $name eq 'DBD';
Ignore that, it is not (yet) used and simply copy-paste-d from
somewhere else
> which seemed to me moving past the current spec in ways I was a little
> uncomfortable about.
I/we cannot go beyond where John and I have gone so far, till we get
wider support from the DBI level
> and Oracle:
>
> o seemed to be using a global integer dbd_oracle flag
> o had a lot of "if (DBIS->debug >= 2 || dbd_verbose >= 2 )"
>
> and I was rather hoping it had ended up fitting into the existing
> DBIc_TRACE macros somehow as I converted to use that last time the
> tracing changed.
We cannot go changing more until the path has been defined. I also
would love to go the way I proposed, but that doesn't make any sense if
not understood froma DBI perspective.
--
H.Merijn Brand Amsterdam Perl Mongers http://amsterdam.pm.org/
using & porting perl 5.6.2, 5.8.x, 5.10.x, 5.11.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, SuSE 10.1, 10.2, and 10.3, AIX 5.2, and Cygwin.
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/
http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
