Ah, you got me onto something there!
It appears that the collation_connection was utf8_general_ci, but all other
collation variables (global and session) were latin_swedish_ci
character set(s) were a mixture of utf8 and latin. bah!!
I've forced the character set and collation in the /etc/my.cnf file to utf8
(_general_ci) and its working fine now.
thanks for the pointer :D
B.
Reggie Burnett wrote:
> Barry
>
> Haven't been able to reproduce this yet. What are the values of all your
> character_set variables on the server?
>
> -reggie
>
>
>>-----Original Message-----
>>From: Barry Zubel [mailto:barry@stripped]
>>Sent: Monday, January 10, 2005 6:17 AM
>>To: dotnet@stripped
>>Subject: Using the UKP sign in mediumtext columns
>>
>>An odd one, and perhaps due to my configuration so I'll list what I have
>>here:
>>
>>Mysql 4.1.8 running UTF8_GENERAL_CI collation
>>a Table with UTF8_GENERAL_CI collation
>>a MEDIUMTEXT field within the table with UTF8_GENERAL_CI collation
>>
>>
>>Connector/Net 1.0.3
>>
>>
>>My problem:
>>
>>Trying to insert a record into the MEDIUMTEXT field in the database that
>>contains a £ sign (thats a UKP sign to those of you whose character sets
>>wont
>>display it) truncates the field at the character before the £ sign.
>>
>>Now, its highly likely that I've done something wrong with the
>>configuration
>>of the MySQL server (I upgraded through 4.0.18 to 4.1.8 and ran all the
>>appropriate upgrade scripts, afaik) with regards to the collation.
>>
>>Anyhows - anyone else seen this, or able to reproduce it?
>>
>>Ta muchly.
>>
>>B.
>>
>>--
>>MySQL on .NET Mailing List
>>For list archives: http://lists.mysql.com/dotnet
>>To unsubscribe: http://lists.mysql.com/dotnet?unsub=1
>
>
>
>
