in reply to Re^2: DBIx returns question marks
in thread DBIx/DBI returns question marks
Hi, me again,
Thanks Corion for giving me this list. This one's a keeper :) I went through it and here's what I have:
I've connected staging machine to use dev DB so both scripts are using the same DB. I've also removed DBIx from equation because I have the same behaviour on DBI, so I'll change the thread title shortly.
Corion: Check the data format in your script as it writes to its output. Is it properly encoded from Unicode to the target encoding? Compare the hexdumps.
Me: Dev -> var is UTF8, endoded:\x{7f16}\x{53f7} hex:e7bc96e58fb7, Stg -> var is not UTF8, var:??, hex:3f3f
Corion: Check the data format in your script as it reads the data from the database. Is it utf8 everywhere? Compare the hexdumps.
Me: No, the ?? variable is not UTF8 when I get it from staging machine
Corion: Check the data format in your database in all tables. Are the tables/columns declared to be utf8/Unicode everywhere? Compare the hexdumps.
Me: I'm using the same database, but different machine. Dev is using local DB and staging is using dev's DB. So that should be covered.
Corion: Check the data format when it is written from your script to the database. Do they write utf8/Unicode everywhere? Compare the hexdumps.
Me: Same as previous answer - same DB, different machine
Corion: Check the data format from where your script gets its data. Is it properly decoded from the source to utf8 everywhere? Compare the hexdumps.
Me: Also covered by previous answer
Well, fighting with this continues. My more experienced colleague is coming from holiday this afternoon. He'll be fresh pair of eyes on this issue.
Stepamil
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: DBIx returns question marks
by Corion (Patriarch) on Aug 08, 2011 at 13:55 UTC | |
|
Re^4: DBIx returns question marks
by stepamil (Acolyte) on Aug 08, 2011 at 17:45 UTC |