On Wed, Oct 29, 2003 at 10:05:46PM -0500, Rudy Lippan wrote:
> On Wed, 29 Oct 2003, Tim Bunce wrote:
>
> > On Tue, Oct 28, 2003 at 04:39:59PM -0500, Rudy Lippan wrote:
> > > >
> > > > Also, I am taking requests for features to be added in the next version of
> > > > DBD::mysql; The list, as of ri
Thanks Steffen.
Tim.
On Wed, Oct 29, 2003 at 09:19:44AM +0100, Steffen Goeldner wrote:
> Tim Bunce wrote:
> >
> > On Mon, Oct 27, 2003 at 04:50:18PM +0100, Steffen Goeldner wrote:
> > >
> [...]
> > >
> > > Three cases cross my mind:
> > >
> > > 1) Return nothing (or an arbitrary value), i.e. th
Hi,
I've added your patch to GBorg.
Thanks,
jas.
Tavin Cole <[EMAIL PROTECTED]> writes:
> i'm running a script that uses DBD::Pg 1.22 and fails with:
>
> Undefined subroutine &DBD::Pg::db::pg_server_version called at
> /usr/lib/perl5/site_perl/5.8.0/i686-linux/DBD/Pg.pm line 911.
>
> this is
Hi,
Is it correct to say that, insofar as ORACLE is supposed to automatically index all
the primary keys, the fact of using a VARCHAR2(256) as primary key field, instead of
smaller type, will actually have no effect on performance?
Thanks
Jean
Accédez au courrier électronique de La Poste : ww
On Thu, 30 Oct 2003 14:05:25 +0100 "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Is it correct to say that, insofar as ORACLE is supposed to
> automatically index all the primary keys, the fact of using a
> VARCHAR2(256) as primary key field, instead of smaller type, will
> actually have no eff
On Thu, 30 Oct 2003, Tim Bunce wrote:
> Er, I don't follow you. I sent you the code to colum_info and it's
> already in DBD::mysql.
>
table_info, table_info() At least that is what I wrote on my
white-board; I don't what I was thinking when I wrote that...
And If I am still not remembering co
