Try http://homepage.eircom.net/~timbunce/DBD-Oracle-1.16-rc7-20040826.tar.gz
and read the documentation about unicode carefully.
Let me know how it goes.
Tim.
On Thu, Oct 14, 2004 at 04:06:41PM -0700, Susan Cassidy wrote:
Hello,
I have a cgi application that works fine using DBD::Pg to
On Tue, 2004-10-12 at 01:05, Tim Bunce wrote:
On Mon, Oct 11, 2004 at 02:16:16PM -0600, Alan Sparks wrote:
I've seen several posting regarding problems people have seen on Linux
with Oracle 9 client libraries and DBD::Oracle, causing an ORA-03113
end-of-file on communication channel error
The good thing is my installation was perfect as I can connect to different Oracle dbs
now.
But I have one different question. For Linux or Windows , do I need to do anything
different other than DBI and DBD driver istallation being little different?
Regards,
Mano
-Original Message-
On 2004-10-14 16:06:41 -0700, Susan Cassidy wrote:
I have a cgi application that works fine using DBD::Pg to insert/select data
from a PostgreSQL using UTF-8 (database created as UNICODE). We have data
in multiple languages stored, which has been working fine.
I have modified the
On 2004-10-15 10:06:03 -0600, Alan Sparks wrote:
Looks like the obvious solution is to downgrade Oracle libraries but
getting the 8.1.7 installer to run on RHEL 3 seems like it'll be a
battle in itself (damn glibc symbols problems).
It seems to be only a problem with the installer, not
On Fri, Oct 15, 2004 at 10:06:03AM -0600, Alan Sparks wrote:
On Tue, 2004-10-12 at 01:05, Tim Bunce wrote:
On Mon, Oct 11, 2004 at 02:16:16PM -0600, Alan Sparks wrote:
I've seen several posting regarding problems people have seen on Linux
with Oracle 9 client libraries and DBD::Oracle,
Actually, I have had a similar problem. I can read utf8 characters from the database
but can't put them in the database using Perl. My system data is: Fedora Core 1,
Perl 5.8.1, DBI 1.43, DBD::Oracle 1.15, Oracle client 9.2.x.
Peter J. Holzer [EMAIL PROTECTED] 10/15 4:29 am
On
On Fri, 2004-10-15 at 10:53, Tim Bunce wrote:
Doesn't look like Oracle has published a solution :-/ Wondering if
there's some way to bypass the describe or maybe somehow reorder to get
past their problem. Will try to get the DBA to call on the bug and see
if there's any new info.
Try
