Hello. Chris, the collation is subordinated to the character set. You should work with the character sets, and only after with collations. The data which you store in your table is silently converted to ascii character set. Are you sure that the characters which you want to store are present in ascii character set? You should change the character set of the fields of your table to that one which can hold non English characters. Another question - are you sure that the data which you're passing to MySQL is in latin1 encoding? See: http://dev.mysql.com/doc/refman/5.0/en/charset-connection.html http://dev.mysql.com/doc/refman/5.0/en/charset-general.html
How to change the character set of the fields is described at: http://dev.mysql.com/doc/refman/5.0/en/alter-table.html Chris wrote: > I'm sorry but I do not know what you mean by NO_TABLE_OPTIONS in > @@sql_mode). > > The database has a Collation = ascii_general_ci. The only other option is > ascii_bin. > > With respect to the table, it also has Collation of the same, > ascii_general_ci. There are many Collation types which the table may be > change to, including several of the utf8 verity (utf8.bin, > utf8.danish.ci,....) but no utf8 without an extension. I tried setting the > table to utf8.unicode.ci, but still encounter the INSERT error as before. > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
