I found an older post on the PostgreSQL mailinglist with same problems
http://www.postgresql.org/message-id/d960cb61b694cf459dcfb4b0128514c207bb6...@exadv11.host.magwien.gv.at
And I was able to fix the issue by dumping and re-importing the db!
# Create empty PG-DB
rt-setup-database --action c
Hi,
you are right.
History is not affected but Subject, User Real Name, Signature stored in
User Preferences, Description of Scrips, Templates, Groups and Queues,
Template Content, Article Name
I noticed that the problem with the german umlauts is not in all fields.
In my history for example
I have the same problem. I want to migrate my RT 4.2.12 mysql-database to
postgres. Did you find an solution for this problem?
I noticed that the problem with the german umlauts is not in all fields. In
my history for example the german umlauts displayed correctly but in the
ticket subject they di
I'm now testing to serialize mysql and import to mysql again.
This is working, so it's a problem with Pg
smime.p7s
Description: S/MIME Cryptographic Signature
RT 4.2.8 and MySQL: old and new tickets looks perfectly, also the
serialized data seems to be ok.
With locale LANG=en_US.UTF-8
^^test ticket with umlaut ü^@^@^@^GSubject
locale LANG=POSIX
^^test ticket with umlaut ^@^@^@^GSubject
Maybe rt-importer or perl opens the binary files with wron
On 9/17/15 8:12 AM, Maik Nergert wrote:
Hexcode from ü → c3 bc
is encoded again to → c3 83 (Ã) and c2 bc (¼)
(http://www.utf8-zeichentabelle.de/)
First I've upgraded RT from 3.8 to 4.2 with mysql db (utf8) and
everything went smoothly.
Can you confirm that the umlaut can be sucessfully added
Hi RT Users,
I'm testing the migration from MySQL to PostgreSQL and I'm experiencing
problems with LATIN1 characters (particularly German umlauts) after the
migration. They look like ü instead ü
Hexcode from ü → c3 bc
is encoded again to → c3 83 (Ã) and c2 bc (¼)
(http://www.utf8-zeichentabe
