Initial testing looks OK in the following, all against a
WE8ISO8859P15/AL16UTF16 10.2.0.2 database, NLS_LANG=.WE8ISO8859P15 (not
tried other NLS combinations yet):

    Cygwin (Perl 5.8.7, DBI 1.51, gcc 3.4.4)
        9.2.0.8 full client 
        10.2.0.2 instant client

    Linux (Perl 5.8.8, DBI 1.52, gcc 3.4.6)
        10.2.0.2 full client

    Windows (ActiveState Perl 5.8.8, DBI 1.5.2, MS Visual Studio.NET 2003)
        10.2.0.2 instant client
        10.2.0.1 xe client

 Test FAILs on:

    Windows (ActiveState Perl 5.8.8 build 817, DBI 1.5.2, MS Visual
Studio.NET 2003)
        9.2.0.8 full client

t/24implicit_utf8.......ok 1/74
#   Failed test 'byte_string test of row 4: column: nch  (uft8) smiley face'
#   in t/nchar_test_lib.pl at line 341.
#          got: '38|58'
#     expected: '226|152|186'

t/24implicit_utf8.......NOK 34#   Failed test 'nice_string test of row 4:
column
: nch  (uft8) smiley face'
#   in t/nchar_test_lib.pl at line 344.
#          got: '&:'
#     expected: '\x{263A}'
#    row 4: DUMP(nch) = Typ=1 Len=4: 0,38,0,58

#   Failed test 'byte_string test of row 4: column: nch  (uft8) smiley face'
#   in t/nchar_test_lib.pl at line 341.
#          got: '38|58'
#     expected: '226|152|186'

#   Failed test 'nice_string test of row 4: column: nch  (uft8) smiley face'
#   in t/nchar_test_lib.pl at line 344.
#          got: '&:'
#     expected: '\x{263A}'
#    row 4: DUMP(nch) = Typ=1 Len=4: 0,38,0,58
t/24implicit_utf8.......NOK 71# Looks like you failed 4 tests of 74.
t/24implicit_utf8.......dubious
        Test returned status 4 (wstat 1024, 0x400)
DIED. FAILED tests 33-34, 70-71
        Failed 4/74 tests, 94.59% okay

 (all other tests OK)

 These tests also fail in the same configuration with DBD-Oracle 1.18a and
1.17 so it doesn't look like a totally new problem.

 The 2nd and 4th failures have:

#     expected: '\x{263A}'
#    row 4: DUMP(nch) = Typ=1 Len=4: 0,38,0,58

 0,38,0,58 is 0x0, 0x26, 0x0, 0x3a - some sort of confusion between UTF-8
and the UTF-16 nchar encoding?

 Similarly with the 1st and 3rd failures:

#          got: '38|58'
#     expected: '226|152|186'

 It's expecting the UTF-8 encoding of \x{263A}, but it's getting the UTF-16
encoding of it.

 Why it's only showing on Windows native and not Cygwin I don't know. I
haven't got a 9.2 Linux client installed at the moment so can't check if it
fails there yet.

-- 
Andy Hassall :: [EMAIL PROTECTED] :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool

-----Original Message-----
From: John Scoles [mailto:[EMAIL PROTECTED] 
Sent: 05 October 2006 16:27
To: dbi-dev@perl.org
Subject: ANNOUNCE: DBD::Oracle 1.19 release candidate

http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.19-RC1.zip

Changes in DBD-Oracle 1.19 (scn rev 7879)

  Fixed execute_array to comply with DBI standard from Martin J. Evans, Xho 
Jingleheimerschmidt and others
  Fixed execute_array so it will not throw a Perl warning on undef values in

Tuples from John Scoles
  Fixed some typos in code and READMEs from John Scoles
  Fixed a few other little bugs dealing with  compatibility with Oracle 8
  Changes to README from Karl Auer
  Suppress warning in 26exe_array.t from Philip Garrett
  Added support for array context aware execute_for_fetch from Martin J. 
Evans

Any and all testing would be greatly appreciated, but especially
testing of building against Oracle Instant Client and Oracle XE
on a range of platforms.

Please take this opertunitry to try out mass updates with execute_array.

Thanks!

John Scoles


Reply via email to