Re^2: Mugged by UTF8, this CANNOT be right

I was under the impression that the none of the DBDs (give the option to) decode text fetched from the database. This is unfortunate, because it means we need to know the encoding the DB uses. Are you saying that some DBDs do decode text?

A number of DBD's dencode the data returned from the database including DBD::ODBC (in a unicode build of it or when instructed to with handle flags), DBD::Oracle, DBD::Pg and DBD::mysql. There may be others.

Comment on Re^2: Mugged by UTF8, this CANNOT be right

Replies are listed 'Best First'.
Re^3: Mugged by UTF8, this CANNOT be right by ikegami (Patriarch) on Jan 27, 2011 at 16:54 UTC
I corrected myself already, but it's not nearly as functional as you make it sound. See the linked post.	[reply]
Re^4: Mugged by UTF8, this CANNOT be right by mje (Curate) on Jan 27, 2011 at 17:34 UTC
Could you point me specifically at the "linked post" as I'm not sure which one you are referring to so I cannot comment on how functional it is that respect - thanks. However, I am using DBD::ODBC and DBD::Oracle to insert and retrieve unicode data to/from many databases with no encoding issues anyone has mentioned here. As far as I am concerned it does just work so long as you get your database set up correctly.	[reply]
Re^5: Mugged by UTF8, this CANNOT be right by mje (Curate) on Jan 27, 2011 at 17:37 UTC
Sorry, I guess you mean this one, yes?. EDITED - got the link wrong.	[reply]
Re^6: Mugged by UTF8, this CANNOT be right by ikegami (Patriarch) on Jan 27, 2011 at 17:57 UTC
Re^7: Mugged by UTF8, this CANNOT be right by mje (Curate) on Jan 27, 2011 at 18:54 UTC
Some notes below your chosen depth have not been shown here