From: Thomas A. Lowery <tl-lists@stlowery.net>
To: pgsql-interfaces@postgresql.org
To: dbi-dev@perl.org
Subject: Re: ANNOUNCE: DBD::Pg 1.20
Date: Sun, 01 Dec 2002 11:58:14 -0500
Message-ID: <20021201165814.GA18541@stllnx1.stlowery.net> (raw)
In-Reply-To: <Pine.LNX.4.50.0211301938040.29663-100000@urth.org>
References: <84A43EBC-0235-11D7-929B-0003931A964A@wheeler.net>
<Pine.LNX.4.50.0211291336140.29663-100000@urth.org>
<87k7ivt0f6.fsf@openinformatics.com>
<20021130204742.GA17239@stllnx1.stlowery.net>
<Pine.LNX.4.50.0211301938040.29663-100000@urth.org>
On Sat, Nov 30, 2002 at 07:38:52PM -0600, Dave Rolsky wrote:
> On Sat, 30 Nov 2002, Thomas A. Lowery wrote:
>
> > On Sat, Nov 30, 2002 at 10:47:09AM -0700, Jason E. Stewart wrote:
> > > "Dave Rolsky" <autarch@urth.org> writes:
> > >
> > > > I found a bug in the ->tables method. It includes all the system tables.
> > > > A patch is at the bottom of the message.
> >
> > I modified the tables and table_info methods to include the system tables.
>
> Why? It's really pretty irritating since they _always_ will be included.
> And you didn't modify the docs to match, since they still say that they're
> _not_ included.
My mistake on the docs, I'll correct them. I find it irritating that the
systems tables are NOT included. Is there a good reason to exclude them?
The advance meta data methods provide a means to write portable code across
the different drivers, let's not leave DBD::Pg out.
Tom
--
Thomas A. Lowery
See DBI/FAQ http://xmlproj.dyndns.org/cgi-bin/fom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tl-lists@stlowery.net, dbi-dev@perl.org
Subject: Re: ANNOUNCE: DBD::Pg 1.20
In-Reply-To: <20021201165814.GA18541@stllnx1.stlowery.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox