Just as a quick reminder regarding character encoding as it seems to be an open PR.
This post in Google Groups describe the issue and the assigned ( PR# is 32482):
https://groups.google.com/forum/?fromgroups=#!searchin/fmetalk/postgis$20norwegian/fmetalk/065X7nSE828/2SseKC6pSPsJ
As a side note - I really hope that they will not delete all posts on groups.google.com/fmetalk - there are many usefull tips here!
Hi all,
Most, if not all, character encoding issues around Postgis have been resolved in the latest FME 2013 beta build available from our download site at
http://www.safe.com/beta. This includes PR#32482 (Encoding issues with the Joiner) referenced by @Sig Till and also PR#38371 (Encoding issues with the Postgis reader/writer).
We have tested this here with Postgis 2.0 and Postgis 1.5. So any feedback from customers would be really useful. Please send it through to us via
http://www.safe.com/supportrequest - along with some sample data.
In reference to the side note - the former FME Talk will be around for a long time in Read Only mode. @Sig Till is correct in that there is lots of useful, relevent information in that archive.
Cheers,
Robyn Rennie
FME Desktop Support
www.safe.com/supportrequest
Is it possible in the writer to run a sql query before writing actual data?
PostgreSQL support conversion between encodings:
http://www.postgresql.org/docs/8.1/static/multibyte.html
Lets say I'm writing to a LATIN1 database I can execute "SET CLIENT_ENCODING TO 'UTF8';" in the same database session.
I still haven't tested the new FME 2013 but I will soon...
/Morten