Slony1 PostgreSQL Replication - Re: encoding=UNICODE db have same chinese handle

You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author

Re: encoding=UNICODE db have same chinese handle

Ian Burrell

2005-07-26, 8:25 pm

On 7/25/05, Sun.betty <alanxzq@yahoo.com.cn> wrote:
> in addition , I test for
> createdb -E UNICODE test
> master and slave as the same.
> export PGCLIENTENCODING=UNI
CODE
> I find as the same question.
> at master :
> insert into T_NUM_CENTER (TYPE , CURRVAL , CURRDATE , MEMO) values
> ('¶«ÃØÃÜÃ×Ã×' , 1 , now() , '¶«¶«¶«');
> at slave
> select * from T_NUM_CENTER ;
> type | currval | currdate | memo
> ------------+---------+------------+------------------------
> ¶«ÃØÃÜÃ× | 1 | 2005-07-25 | ¶«¶«¶«

That is the sympton of the bug. The bug in the trigger truncates
strings with multi-byte characters. It ends up removing one byte for
each multi-byte character in the strings. My guess is that this was
enough to remove the last Chinese character.

- Ian

Sponsored Links