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)
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.
|