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.


The way forward always starts with a minimal test.

In reply to Re^2: Postgres UTF-8 woes by 1nickt
in thread Postgres UTF-8 woes by 1nickt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.