On Tue, Feb 11, 2003 at 02:38:06PM +, Tim Bunce wrote:
ok 102 at line 316
fetchrow_hashref('NAME_uc')
ok 103 at line 319
Insecure dependency in parameter 1 of
DBI::st=HASH(0x1c1100)-FETCH method call while running with -T
switch at t/10examp.t line 320.
OK, I managed to
On Wed, Feb 12, 2003 at 10:57:29PM +1100, Bradley Baetz wrote:
On Tue, Feb 11, 2003 at 02:38:06PM +, Tim Bunce wrote:
ok 102 at line 316
fetchrow_hashref('NAME_uc')
ok 103 at line 319
Insecure dependency in parameter 1 of
DBI::st=HASH(0x1c1100)-FETCH method call while
On Wed, Feb 12, 2003 at 12:52:25PM +, Tim Bunce wrote:
On Wed, Feb 12, 2003 at 10:57:29PM +1100, Bradley Baetz wrote:
Thanks for digging into this!
Here's something I wrote previously that may give some ideas:
Hmm. In what context was this written? :)
Something is causing the perl
On Thu, Feb 13, 2003 at 12:36:04AM +1100, Bradley Baetz wrote:
On Wed, Feb 12, 2003 at 12:52:25PM +, Tim Bunce wrote:
On Wed, Feb 12, 2003 at 10:57:29PM +1100, Bradley Baetz wrote:
Thanks for digging into this!
Here's something I wrote previously that may give some ideas:
Hmm.
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
Here is the UTF8 patch. Is this something we want to apply now?
---
Dominic Mitchell wrote:
Before christmas, I started a thread in dbi-users about the support for
setting the utf8 flag on returned values[1]. I've got
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
14 matches
Mail list logo
