On Tue, Dec 21, 2004 at 08:28:43PM -0500, Lincoln A. Baxter wrote:
> Hi Alan,
>
> Can you turn this script into a test using t/23wide_db_al32utf8.t
> as a model. You could call it t/23wide_db_al32uft8_sp.t
> Please send it to me (and Tim).
>
> If you do, one of us can take a closer look. I think
Hi Alan,
Can you turn this script into a test using t/23wide_db_al32utf8.t
as a model. You could call it t/23wide_db_al32uft8_sp.t
Please send it to me (and Tim).
If you do, one of us can take a closer look. I think the problem,
however, is the we have no way to know, what the VARCHAR2 being ret
However, if the same data selected is done via a stored procedure, the
strings returned have their internal utf8 flag turned off. What I can
then do is use _utf8_on in the Encode module to turn the flag on, but
of course I would rather not have to.
Are there other users with similiar set-ups succe
DBD::Oracle 1.16
Oracle 10g (client 10.1.0.3)
Red Hat Enterprise Linux ES release 3 (Taroon Update 3)
Perl 5.8.6 (multithreaded disabled)
NLS_LANG="AMERICAN_AMERICA.AL32UTF8";
NLS_NCHAR="AL32UTF8"
I have found on my system that when I execute a SQL select statement,
that the strings returned have
