[6.1.6 / PostgreSQL] Invalid byte sequence for encoding "UTF8": 0xe9 0x71 0x75.

[swierzbicki]

Here is what I've found so far :

I haven't called "FConnection.Connect" nor in my SetConnection method nor in any other methods used in my class. I'm sure that this caused all my problems and thing were later messed up, bringing us the cryptic "Invalid byte sequence for encoding "UTF8": 0xe9 0x71 0x75" exception message !

By chance, I found that something was wrong with my table "productions_plateaux_details".
I have previously inserted thousand of records into this table. This table has an SERIAL field. Last ID was something like 5000 BUT the sequence function attached to it returned a currval value of 300... : as a result, each data inserted into this table failed with this error

Code: Select all

ERREUR: La valeur d'un clé dupliquée rompt la contrainte unique "productions_matieres_details_pkey"

BUT UniDAC throw this one

Code: Select all

"Invalid byte sequence for encoding "UTF8": 0xe9 0x71 0x75" 

The right error message was raised when calling an initial "FConnection.Connect".

There is still a small issue now, UniDAC isn't able to display accentuated characters. This message is raised

Code: Select all

"ERREUR: La valeur d'un cl? dupliqu?e rompt la contrainte unique "productions_matieres_details_pkey""

instead of

Code: Select all

"ERREUR: La valeur d'un clé dupliquée rompt la contrainte unique "productions_matieres_details_pkey""

[azyk]

We have fixed this problem. This fix will be included in the next UniDAC build.

[swierzbicki]

Thank you.

Will new version released tomorrow ?

[azyk]

UniDAC release is planned for the next week.