Hi choroba, thank you for replying.

Client and server encoding are both set to UTF-8:

Activity=# \l
                                List of databases
   Name    |  Owner  | Encoding |   Collate   |    Ctype    |  Access 
+privileges
-----------+---------+----------+-------------+-------------+---------
+------------
 Activity  | ******* | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 postgres  | ******* | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 template0 | ******* | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/*****
+**         +
           |         |          |             |             | *******=
+CTc/*******
 template1 | ******* | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/*****
+**         +
           |         |          |             |             | *******=
+CTc/*******
(6 rows)

Activity=# show client_encoding;
 client_encoding
-----------------
 UTF8
(1 row)
[download]

The data is passed decoded from UTF-8, which I believe is correct. DBIx seems to handle it as expected (given the encodings specified in the schema), but the SQL then produced by DBD::Pg/DBI is garbled, as shown. Passing data encoded to UTF-8 to DBIx results in even more garbled content in the DB.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.