I meant to say Already applied by someone else --- not me.
---
Dominic Mitchell wrote:
Tim Bunce wrote:
Ah, you're passing it the address of (probably temporary) reference.
It's the underlying object (which the ref
developers' [EMAIL PROTECTED]
Subject: Re: DBD::Pg 1.30_1 WAS (Re: [INTERFACES] Prepare and prepare ?)
It is back up now --- Marc installed a new kernel.
Also, with our current CVS of DBD:pg, perl 5.005_03 can no longer do
'gmake test'. I get:
PERL_DL_NONLAZY=1 /usr/bin
Rudy Lippan wrote:
Also, with our current CVS of DBD:pg, perl 5.005_03 can no longer do
'gmake test'. I get:
PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
-I/usr/libdata/perl5/5.00503/i386-bsdos -I/usr/libdata/perl5/5.00503 -e
'use Test::Harness qw(runtests
It is back up now --- Marc installed a new kernel.
Also, with our current CVS of DBD:pg, perl 5.005_03 can no longer do
'gmake test'. I get:
PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
-I/usr/libdata/perl5/5.00503/i386-bsdos -I/usr/libdata/perl5/5.00503 -e
Tim Bunce wrote:
On Fri, May 30, 2003 at 03:13:04PM +0100, Dominic Mitchell wrote:
Tim Bunce wrote:
On Fri, May 30, 2003 at 10:20:11AM +0100, Dominic Mitchell wrote:
See, I told you I wasn't an XS guru. :-)
Actually, I looked at this, but my limited C and DBI skills couldn't
work out a) what
On Mon, Jun 02, 2003 at 02:27:13PM +0100, Dominic Mitchell wrote:
Well, we're calling PQsetNoticeProcessor[1], from inside dbd_db_login,
so I should be able to pass in imp_dbh as the arg argument. The bit
that I wasn't sure about before was what to cast it to in order to
retrieve it from a
On Thu, 29 May 2003, Dominic Mitchell wrote:
And for anyone who is interested here is the change log:
One more thing for the change log: notice messages generated by the
database now use the perl warning mechanism instead of going to stderr,
so they can be trapped if needed.
Added
On Fri, May 30, 2003 at 03:13:04PM +0100, Dominic Mitchell wrote:
Tim Bunce wrote:
On Fri, May 30, 2003 at 10:20:11AM +0100, Dominic Mitchell wrote:
See, I told you I wasn't an XS guru. :-)
Actually, I looked at this, but my limited C and DBI skills couldn't
work out a) what the required
On Thursday, May 29, 2003, at 01:57 AM, Rudy Lippan wrote:
On Mon, 26 May 2003, Bruce Momjian wrote:
Rudy, where are we on the release of DBD:pg withs your patches? Are
they ready to go?
I spun an ALPHA copy of DBD::Pg. So much has changed in there that I am
sure something is broken for
On Thursday, May 29, 2003, at 02:00 AM, Dominic Mitchell wrote:
One more thing for the change log: notice messages generated by the
database now use the perl warning mechanism instead of going to
stderr, so they can be trapped if needed.
Oh, sweet! How did you do that? I've been doing this to
Rudy Lippan wrote:
On Mon, 26 May 2003, Bruce Momjian wrote:
Rudy, where are we on the release of DBD:pg withs your patches? Are
they ready to go?
I spun an ALPHA copy of DBD::Pg. So much has changed in there that I am
sure something is broken for someone; therefore, I think we should let
David Wheeler wrote:
On Thursday, May 29, 2003, at 02:00 AM, Dominic Mitchell wrote:
One more thing for the change log: notice messages generated by the
database now use the perl warning mechanism instead of going to
stderr, so they can be trapped if needed.
Oh, sweet! How did you do that?
On Thu, May 29, 2003 at 10:00:21AM +0100, Dominic Mitchell wrote:
One more thing for the change log: notice messages generated by the
database now use the perl warning mechanism instead of going to stderr,
so they can be trapped if needed.
Hopefully implemented as
if
On Mon, 26 May 2003, Bruce Momjian wrote:
Rudy, where are we on the release of DBD:pg withs your patches? Are
they ready to go?
I spun an ALPHA copy of DBD::Pg. So much has changed in there that I am
sure something is broken for someone; therefore, I think we should let
people hammer on it
These all sounds good. Can I get some of them as patches I can apply
now --- having one megapatch usually gets too complex after a while.
---
Rudy Lippan wrote:
On Fri, 14 Mar 2003, Bruce Momjian wrote:
To answer
On Wed, 26 Mar 2003, David Wheeler wrote:
On Wednesday, March 26, 2003, at 07:47 PM, Rudy Lippan wrote:
So I guess what I am propsing is get 1.22 out (if we even think it is
needed -- I think that we can just get away with putting the UTF-8
stuff
off until 1.3) and then drop
On Fri, 14 Mar 2003, Bruce Momjian wrote:
To answer your question from a month ago :-), we should have CVS tagged
the 1.21 release, but we forgot. I didn't think we were big enough to
tag things. :-)
Bruce,
To respond to your message of a week or so ago :-)
I tagged it up a while ago --
To answer your question from a month ago :-), we should have CVS tagged
the 1.21 release, but we forgot. I didn't think we were big enough to
tag things. :-)
We don't have any master plan on development --- we just discuss items
and apply patches.
On Thu, 13 Feb 2003, Dominic Mitchell wrote:
Well at the moment, backwards compatibility is limited to one system at
our place that needed the funtionality right now. We'll change it to
use whatever DBD::Pg comes with, however.
Right, but once it goes into a public release (eg. DBD::Pg
On Saturday, February 15, 2003, at 07:46 AM, Rudy Lippan wrote:
1. Looking over CVS I don't see a release tag for 1.21. It would
proably
be better for whoever did the export of 1.21 to tag up, but if you
want I
will set up a release tag for 1.21?
Yes, please. Use the same tagging style as
On Wednesday, February 12, 2003, at 11:13 PM, Rudy Lippan wrote:
I am game with that. But I'd still like to do some research on the
issue,
and I would also like make sure that DBD::Pg goes they way DBI goes.
So I
don't want to rush and end up with a bad interface or one that differs
from the
On Tuesday, February 11, 2003, at 10:51 PM, Rudy Lippan wrote:
Since David is too busy to work on DBD::Pg right now, I have ported the
changes that I made against 1.13 to CVS HEAD from gborg.postgresql.org.
The patch can be found here:
http://www.remotelinux.com/rlippan/dbd_pg.patch (I did not
On Wed, 12 Feb 2003, David Wheeler wrote:
I'd like to start putting together some developer releases (set up a
cvs
branch for this?), and see about getting together a stable release
version
that addresses the all of the outstanding problems with DBD::Pg.
So, if people are
On Wed, 12 Feb 2003, Dominic Mitchell wrote:
David Wheeler wrote:
On Tuesday, February 11, 2003, at 10:51 PM, Rudy Lippan wrote:
Known problems with patch:
1. Broke new pg_bool_tf attribute.
Ah. Can be fixed, I assume?
Should be easily. My pg_do_utf8 patch clashed with it.
On Wed, 12 Feb 2003, David Wheeler wrote:
On Wednesday, February 12, 2003, at 07:42 PM, Rudy Lippan wrote:
Oh, well we can create a branch for the old version. Bruce, do you have
a CVS tag convention that you like to use?
As for CPAN, should I go ahead set up a PAUSE account (I need to
On Wed, 12 Feb 2003, David Wheeler wrote:
On Wednesday, February 12, 2003, at 08:45 PM, Rudy Lippan wrote:
Just did a quick look a the patch and the Pgsql docs. I need to do
some
more research, but what do you think about a set_client_encoding()
function tells the db that you want
David Wheeler wrote:
On Wednesday, February 12, 2003, at 07:42 PM, Rudy Lippan wrote:
I was thinking more for bug fixes agaist the old version before the
devel release are tested enough to go to production.
Oh, well we can create a branch for the old version. Bruce, do you have
a CVS
On Wednesday, February 12, 2003, at 08:49 PM, Bruce Momjian wrote:
Let's get the small UTF patch into a DBD:pg release, then we can just
put it all into the main CVS and do a beta/final release with his
changes. I don't see why we need to create a branch.
Works for me...unless Rudy's
On Wed, 12 Feb 2003, David Wheeler wrote:
On Wednesday, February 12, 2003, at 08:49 PM, Bruce Momjian wrote:
Let's get the small UTF patch into a DBD:pg release, then we can just
put it all into the main CVS and do a beta/final release with his
changes. I don't see why we need to
On Wednesday, February 12, 2003, at 10:32 PM, Rudy Lippan wrote:
Tell me your GBorg login name and I'll give it to you.
rlippan
You're now officially a developer. :-)
Maybe I will go over to PostgreSQL hackers and cause some trouble ;)
It is
a *major* pain. I looked at PostgreSQL it
On Thu, 6 Feb 2003, David Wheeler wrote:
Unfortunately I have no time to work on DBD::Pg stuff right now. :-(
I'll have to rely on others to evaluate your approach. Post to the
dbi-dev list, too -- those folks have a better idea on how to implement
DBI drivers, I think.
I hope I can
I just happend upon this message while catching up on pgsql-interfaces...
On Thu, 23 Jan 2003, David Wheeler wrote:
Date: Thu, 23 Jan 2003 17:31:11 -0800
From: David Wheeler [EMAIL PROTECTED]
To: Kaare Rasmussen [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [INTERFACES] Prepare
32 matches
Mail list logo
