Rainer, You can use iconv to strip the offending characters from you dump which will allow it to be imported into 8.2. In our migration, we only had 2 bad characters in 100k tickets. If you find a pattern in the problem characters, you could do a DB update to clean it before the transition, too. Good uck.
Ken On Sat, Jul 28, 2007 at 01:13:02PM +0200, Rainer Duffner wrote: > > Am 28.07.2007 um 08:07 schrieb Rainer Duffner: > > >Hi, > > > >as the subject says. > >I can see the history (who added what when), but I cannot actually > >see the ticket text or the correspondence/comments. > > > >When I create a new ticket, all data is shown. > > > >This is weird. > > > >Does anybody have an idea? > > > > > Hm. upon looking at the tables via phppgadmin and reviewing the > import-logs, I see this error > invalid byte sequence for encoding "UTF8". > > This is for postgresql 8.2 on FreeBSD, and it seems it is hitting > some anti-sql-injection measure, introduced some time ago. > The dump is in the pg_dump compressed native format. > How can I convert it into some "native" SQL, so I can look at the > offending attachment and change the character? > > > > cheers, > Rainer > -- > Rainer Duffner > CISSP, LPI, MCSE > [EMAIL PROTECTED] > > > _______________________________________________ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: [EMAIL PROTECTED] > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
