Hello everyone.
I have to maintain one web application with old and rich history. Originally it ran on CGI, later it was "migrated" to mod_perl2, using ModPerl::Registry. After recent migration on new OS and hardware we faced several bugs, caused by CGI.pm and we decided to switch on mod_perl2 completely. I wrote a simple handler, everything works fine, but now it requires to explicitely decode utf-8 strings, that are fetched from DB (DBD::Firebird) (while previously it worked fine out-of-the-box, decoded them implicitly). What kind of smart stuff ModPerl::Registry does? I swear I didn't touched most of the original code of our application (except CGI.pm imports, now we use own wrapper on top of Apache2::Request).
And I realy don't want to modify hundreds of fetches from DB to explicitly decode utf-8 strings.
P.S. Those strings are passed into Template::Toolkit templater
Source code:
Handler
Wrapper, that replaces CGI.pm
Connection to DB
Best Regards,
Dmitry
In reply to DBD::Firebird, mod_perl2 and utf-8 by kravitz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |