Обсуждение: about encoding

Поиск
Список
Период
Сортировка

about encoding

От
superman0920
Дата:
BLOCKQUOTE {MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em } OL {MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px } UL {MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px } P {MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px }
hello
i want to insert a report to postgresql,the report contain something Chinese characters and the postgresql is utf-8.
the response from db is this:
ERROR:  invalid byte sequence for encoding "UTF8": 0xb1
 
how can i fix it ?
 
thx
 

superman0920

Re: about encoding

От
"Kevin Grittner"
Дата:
superman0920 <superman0920@gmail.com> wrote:

> i want to insert a report to postgresql,the report contain
> something Chinese characters and the postgresql is utf-8.
>
> the response from db is this:
> ERROR:  invalid byte sequence for encoding "UTF8": 0xb1

That's not a valid byte sequence for a character under the UTF8
character encoding scheme.  You said that PostgreSQL is using utf-8,
but what encoding is used for the report?  Is your client connecting
using the character encoding scheme used by the report?

-Kevin

custom conflict resolution information request

От
amador alvarez
Дата:
Hi there,
I am trying to find any kind of information or examples to deal with
custom conflict resolution on swap syncs in a master-master replication.

Any clue will be very wellcome,

Thanks in advance,

Amador A.


Re: custom conflict resolution information request

От
"Kevin Grittner"
Дата:
amador alvarez <aalvarez@d2.com> wrote:

> I am trying to find any kind of information or examples to deal
> with custom conflict resolution on swap syncs in a master-master
> replication.

What are you using for replication?

-Kevin

Re: custom conflict resolution information request

От
amador alvarez
Дата:
What are you using for replication?

-Kevin


Hi Kevin,

I set up a master-master asynchronous replication of one database with bucardo 4.4.5 and testing right now 4.99.3.
I know the standard settings when a conflict between same id rows comes up :

source - the rows on the "source" database always "win" (in a conflict, we copy rows from source to target)


target - the rows on the "target" database always win


skip - any conflicted rows are simply not replicated. Not recommended
for most cases.


random - each database has an equal chance of winning each time


latest - the row that was most recently changed wins


abort - the sync is aborted on a conflict You can also provide custom
conflict handlers to allow you to use business logic for better conflict
resolution.


I have not found info or examples about the custom option yet, and still on the search ...

Cheers,

Amador A.



On 04/02/2012 11:57 AM, Kevin Grittner wrote:
> amador alvarez<aalvarez@d2.com>  wrote:
>
>> I am trying to find any kind of information or examples to deal
>> with custom conflict resolution on swap syncs in a master-master
>> replication.
>
> What are you using for replication?
>
> -Kevin