I *just* tracked down a similar problem in our system.
It turns out that we were receiving data from SOAP::Lite that Perl had
marked internally as UTF-8, even though there were NO characters that
required it.
Another value that was completely UTF-8 clear was being *magically*
transformed by a
Dear Tim (and Jay - there's new info here, Jay),
Jay Konigsberg originally approached me with a problem whereby an o-umlaut
character in some data was being transformed into a two bytes with
different codes. After paring his initial 800-line reproduction down to
just 92 lines of code, I was
On Tue, 17 Jun 2003 15:35:20 -0500, NIPP, SCOTT V (SBCSI) wrote:
Hi Scott
>Thanks again for all the good feedback. If anyone can recommend
a
>good book that could help me out on this I would be most
>appreciative. I
>have some MySQL reference books, but nothing that really goes into
>databa
Hello,
I am using the DBI version 1.37 with the DBD mysql
2.1027 module and perl version 5.8.0 on Solaris 8
(sparc). I am running a script that connects to a
remote mysql database. When run, I get the following
error:
ld.so.1: /usr/local/bin/perl: fatal: relocation error:
file
/usr/local/lib/per
The logic in having a table per user is basically as follows...
Each user would have a table with columns such as UID, GID, home directory,
default shell, date created, etc. Each row would then be an entry with all
of this pertinent information for each server that the user has an account
Lin Feng wrote:
> Have Oracle's SQLX function such as XMLAGG(), XMLELEMENT() been
> impletemented in DBD::Oracle? I got an error (OCIDefinedObject call
> needed but not implemented yet]. This is on Oracle 9.2.
Those functions do not need to be implemented in DBD::Oracle, since they're
executed by
Tim's instructions stated to post when the "standard no option" configure failed so
here goes...
I used a string of ='s to separate the files I cat'd to this email.
Solaris 9 64-bit
Oracle 9.2.0.3 64-bit
perl 5.8.0
output from perl -V:
Summary of my perl5 (revision 5.0 version 8 subversion 0)
Hi,
Have Oracle's SQLX function such as XMLAGG(), XMLELEMENT() been
impletemented in DBD::Oracle? I got an error (OCIDefinedObject call needed but not
implemented yet]. This is on Oracle 9.2.
Thanks,
Lin
-
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per mo
On Tue, Jun 17, 2003 at 05:12:06PM +0200, Brigitte Jellinek wrote:
> > On Tue, Jun 17, 2003 at 11:57:25AM +0200, Brigitte Jellinek wrote:
> > > [...] I write utf-8 into mysql -
> > > that seems to work. but when I read it back, not only do I get
> > > a "classical perl string" instead of an utf8 s
Greetings,
I've been beating my head against a problem here for about a week, and
getting nowhere.
We have a RedHat 7.3 system with perl 5.6.1 installed, and mod_perl 1.27
compiled into Apache as a static module. Everything works fine - EXCEPT
DBI. Any scripts that use DBI bomb out, and the f
> On Tue, Jun 17, 2003 at 11:57:25AM +0200, Brigitte Jellinek wrote:
> > [...] I write utf-8 into mysql -
> > that seems to work. but when I read it back, not only do I get
> > a "classical perl string" instead of an utf8 string, but also some
> > of the bits are broken:
On Tue, Jun 17, 2003 at 1
Yes, use the 32-bit oracle libraries. I will forward a previous post on
this issue.
Thanks,
Sam Gold
-Original Message-
From: Rafael Caceres [mailto:[EMAIL PROTECTED]
Sent: Monday, June 16, 2003 6:54 PM
To: [EMAIL PROTECTED]
Subject: Can't build DBD::Oracle on AIX 5.1 with Oracle 9.2
Please try using another tool (eg mysqldump) to read the data from
the db to check if the problem is related to inserting the data
and/or retrieving it. Also try not using placeholders.
Thanks.
Tim.
On Tue, Jun 17, 2003 at 11:57:25AM +0200, Brigitte Jellinek wrote:
>
> hi!
>
> I'm not sure th
hi!
I'm not sure this is supposed to work yet I write utf-8 into mysql -
that seems to work. but when I read it back, not only do I get
a "classical perl string" instead of an utf8 string, but also some
of the bits are broken:
he string i write into the db is 6 characters long:
"A\N{greek:b
14 matches
Mail list logo