Re: Release of DBD-pg 1.22

On 30/3/03 11:28 pm, "Ian Barwick" <barwick(at)gmx(dot)net> wrote:

> On Saturday 29 March 2003 15:56, Adam Witney wrote:
>> On 28/3/03 3:58 pm, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)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.

Yep, there is no trace of is_utf8_string() in perldoc perlapi for 5.6.0

Does this mean that my only option is to upgrade perl? Or will the module
still work without it?

Thanks for your help

adam

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.