On Fri, Mar 15, 2002 at 04:31:11PM -0800, Jonathan Leffler wrote:
> Dear Tim,
>
> I spotted the discussion about using these attributes to improve the
> performance of DBD::Oracle, and woke up since I don't remember them
> being discussed before.
>
> Running 'perldoc DBI' for DBI 1.21 gives:
>
On Tue, Mar 19, 2002 at 04:41:33PM +0100, Steffen Goeldner wrote:
> Tim Bunce wrote:
> >
> > On Tue, Mar 19, 2002 at 12:20:43PM +0100, Steffen Goeldner wrote:
> > > Tim Bunce wrote:
> > > >
> > > > On Mon, Mar 18, 2002 at 12:05:28PM +0100, Steffen Goeldner wrote:
> > >
> > > > A more realistic ex
Tim Bunce wrote:
>
> On Tue, Mar 19, 2002 at 12:20:43PM +0100, Steffen Goeldner wrote:
> > Tim Bunce wrote:
> > >
> > > On Mon, Mar 18, 2002 at 12:05:28PM +0100, Steffen Goeldner wrote:
> >
> > > A more realistic example would be for drivers that return empty
> > > strings or NULL for the catalog
On Tue, Mar 19, 2002 at 12:20:43PM +0100, Steffen Goeldner wrote:
> Tim Bunce wrote:
> >
> > On Mon, Mar 18, 2002 at 12:05:28PM +0100, Steffen Goeldner wrote:
>
> > A more realistic example would be for drivers that return empty
> > strings or NULL for the catalog portion.
>
> Currently, DBD::O
Tim Bunce wrote:
>
> On Mon, Mar 18, 2002 at 12:05:28PM +0100, Steffen Goeldner wrote:
> A more realistic example would be for drivers that return empty
> strings or NULL for the catalog portion.
Currently, DBD::Oracle's table_info() method returns '' -> NULL ->
undef for the PUBLIC pseudo-sche