On Thu, Aug 30, 2001 at 11:30:23AM -0400, Alex Pilosov wrote:
> On Thu, 30 Aug 2001, Tim Bunce wrote:
>
> > It's my intention to allow the DBI's private install_method() method
> > to be used to install driver-specific methods - so long as the name
> > of the method begins with the drivers own pr
On Thu, 30 Aug 2001, Tim Bunce wrote:
> It's my intention to allow the DBI's private install_method() method
> to be used to install driver-specific methods - so long as the name
> of the method begins with the drivers own prefix (ie ora_ for DBD::Oracle).
Ah, that's a nice solution. Is it alread
On Thu, 30 Aug 2001, Jeff Boes wrote:
> Perhaps related, perhaps not: what is the purpose of the 'tty=' option in
> the driver? I looked at that with an increasingly puzzled expression on my
> face (8-), in hopes that I could use that to capture the output.
Not exactly. This is TTY that backend o
On Thu, Aug 30, 2001 at 07:15:41AM -0700, Randal L. Schwartz wrote:
> > "Alex" == Alex Pilosov <[EMAIL PROTECTED]> writes:
>
> Alex> My tiny annoyance with DBI is (or maybe I don't understand the
> Alex> way DBI works) is that the only way I can add driver-specific
> Alex> functions to DBI ha
On Thu, 30 Aug 2001 10:07:00 -0400 (EDT)
Alex Pilosov <[EMAIL PROTECTED]> wrote:
> On Thu, 30 Aug 2001, Jeff Boes wrote:
>
> > The EXPLAIN SELECT statement will produce, under DBD::Pg, output that
> > looks like
> >
> > NOTICE: QUERY PLAN:
> >
> > Index Scan using emp_pkey on emp (c
> "Alex" == Alex Pilosov <[EMAIL PROTECTED]> writes:
Alex> My tiny annoyance with DBI is (or maybe I don't understand the
Alex> way DBI works) is that the only way I can add driver-specific
Alex> functions to DBI handle is by using $dbh->func('funcname',args),
Alex> which is pretty ugly. Is t
On Thu, 30 Aug 2001, Jeff Boes wrote:
> Does anyone have a slick way to capture the output of an EXPLAIN command
> issued via DBI (specifically, DBD::Pg)?
>
> I'm attempting to extend a query generator so that it can intelligently
> select columns to build a WHERE clause based on a record (hashr
Does anyone have a slick way to capture the output of an EXPLAIN command
issued via DBI (specifically, DBD::Pg)?
I'm attempting to extend a query generator so that it can intelligently
select columns to build a WHERE clause based on a record (hashref)
received. What I want to do is something lik
