On Wed, Oct 20, 2004 at 03:49:25PM +0100, Tim Bunce wrote:
> Yes, another release candidate!
> 
> I think I've finally got to the bottom of the character set issues.

[...]

> I'd be especially grateful for reports of testing of ...
>   - a range of Oracle versions, especially 8.1.x and even 8.0.x

Hello Tim,

This is perl, v5.8.3 built for i386-linux-thread-multi

and

Database and client versions and character sets:
Database 8.0.5.2.1 CHAR set is EE8ISO8859P2 (Non-Unicode), NCHAR set is EE8ISO8859P2 
(Non-Unicode)
Client 9.2.0.0.0 NLS_LANG is '<unset>', NLS_NCHAR is '<unset>'

and I get

t/23wide_db_8bit........set $ENV{NLS_LANG}=AMERICAN_AMERICA.WE8MSWIN1252
dubious
        Test returned status 0 (wstat 11, 0xb)
Scalar found where operator expected at (eval 154) line 1, near "'int'  $__val"
        (Missing operator before   $__val?)

[...]

t/25plsql...............1..83
[...]
ok 65
After p1=[Hello] p2=[Y] p3=[Y]
test nvarchar2 arg passing to functions
Can't call method "bind_columns" on an undefined value at t/25plsql.t line 319.
# failed test 66 at line 318
not ok 66
dubious
        Test returned status 2 (wstat 512, 0x200)
DIED. FAILED tests 66-83
        Failed 18/83 tests, 78.31% okay

[...]

Failed 2/18 test scripts, 88.89% okay. 18/1720 subtests failed, 98.95% okay.
Failed Test        Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t/23wide_db_8bit.t    0    11    ??   ??       %  ??
t/25plsql.t           2   512    83   35  42.17%  66-83
6 tests and 131 subtests skipped.

All other tests are either skipped (it is not a Unicode database)
or passed.

For the same perl and

Database and client versions and character sets:
Database 10.1.0.2.0 CHAR set is AL32UTF8 (Unicode), NCHAR set is UTF8 (Unicode)
Client 9.2.0.0.0 NLS_LANG is '<unset>', NLS_NCHAR is '<unset>'

t/21nchar............... Database and client versions and character sets:
Database 10.1.0.2.0 CHAR set is AL32UTF8 (Unicode), NCHAR set is UTF8 (Unicode)
Client 9.2.0.0.0 NLS_LANG is '<unset>', NLS_NCHAR is '<unset>'
set $ENV{NLS_NCHAR}=WE8ISO8859P1
dubious
        Test returned status 0 (wstat 11, 0xb)
Scalar found where operator expected at (eval 154) line 1, near "'int'  $__val"
        (Missing operator before   $__val?)

[...]

t/23wide_db_8bit........set $ENV{NLS_LANG}=AMERICAN_AMERICA.WE8MSWIN1252
dubious
        Test returned status 0 (wstat 11, 0xb)

[...]

Failed 2/18 test scripts, 88.89% okay. 0/1905 subtests failed, 100.00% okay.
Failed Test        Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t/21nchar.t           0    11    ??   ??       %  ??
t/23wide_db_8bit.t    0    11    ??   ??       %  ??
1 test and 122 subtests skipped.

For a combination of

Database and client versions and character sets:
Database 10.1.0.2.0 CHAR set is AL32UTF8 (Unicode), NCHAR set is UTF8 (Unicode)
Client 10.1.0.2 NLS_LANG is '<unset>', NLS_NCHAR is '<unset>'

all is fine and nice, all tests pass (or are skipped).

Anything I can check (or add more info) concerning the failures on
the 9.2 client?

-- 
------------------------------------------------------------------------
 Honza Pazdziora | [EMAIL PROTECTED] | http://www.fi.muni.cz/~adelton/
 .project: Perl, mod_perl, DBI, Oracle, large Web systems, XML/XSL, ...
                Only self-confident people can be simple.

Reply via email to