Re: Release of DBD-pg 1.22 - Mailing list pgsql-interfaces

From Ian Barwick
Subject Re: Release of DBD-pg 1.22
Date
Msg-id 200303310028.26123.barwick@gmx.net
Whole thread Raw
In response to Re: Release of DBD-pg 1.22  (Adam Witney <awitney@sghms.ac.uk>)
Responses Re: Release of DBD-pg 1.22
List pgsql-interfaces
On Saturday 29 March 2003 15:56, Adam Witney wrote:
> On 28/3/03 3:58 pm, "Bruce Momjian" <pgman@candle.pha.pa.us> wrote:
> > What version of perl do you have?  I have 5.005_03, and others have 5.6,
> > and both seem to work.  The current test in dbdimp.c is:
> >
> > #ifdef SvUTF8_off
> >        if (imp_dbh->pg_enable_utf8) {
> >        SvUTF8_off(sv);
> >        /* XXX Is this all the character data types? */
> >        if (18 == type || 25 == type || 1042 ==type || 1043 == type) {
> >            if (is_high_bit_set(val) && is_utf8_string(val, val_len))
> >            SvUTF8_on(sv);
> >        }
> >        }
> > #endif
> >
> > Maybe that isn't the right test --- maybe you have a version of perl
> > that passes the #ifdef test, but doesn't have is_utf8_string().
>
> I have perl 5.6.0. I don't know if it has is_utf8_string()... Where would I
> look for this?

I'm fuzzy on the details but ISTR Perl 5.6.0 was not one of Perl's better
releases and was replaced fairly quickly with 5.6.1. A bit of googling
returns is_utf8_string() together with 5.6.1 but no references to 5.6. This
is not scientific evidence though.

Can you do "perldoc perlapi" with 5.6.0? If so the presence / absence
of is_utf8_string() should solve the problem.

Ian Barwick
barwick@gmx.net



pgsql-interfaces by date:

Previous
From: Michael Meskes
Date:
Subject: Re: ECPG thread-safety
Next
From: Philip Yarra
Date:
Subject: Re: ECPG thread-safety