Note for MySQL 4.1

This message was edited 3 times. Last update was at 13/11/2004 10:46:10

Hi, just installed 2.0.1 with mysql 4.1. When i tried to register I got a the error

Illegal mix of collations

(utf8_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE)

This looks to be due to changes in mysql 4.1 from 4.0 (see http://mysql.binarycompass.org/doc/mysql/en/Charset-collation-charset.html)

I removed the &useUnicode=true&characterEncoding=UTF-8 from the database url connection (WEB-INF/config/database/mysql/mysql.properties) and it worked ok. Hope this helps someone!

dan

Ok, this is not good. I first thought that upgrading the mysql library to the last development version available ( 3.1.4 ) it will work, but it didn't.
I'll put a section related to this issue in the FAQ until we find a good solution for the problem.

Rafael

This message was edited 1 time. Last update was at 13/11/2004 10:46:27

Here are some more detailed steps about how to change the MySQL configuration file:

Open the file WEB-INF/config/database/mysql/mysql.properties with any text editor

There you will find a key named "database.connection.string" with a big string as a value. Change the value to

Save the file and, if you had configured a connection pool, restart the container.

Rafael

Alternatively, when you create the database, specify utf8 as the default character set, ie:

create database jforum default character set utf8

Regards
Keith

An error has ocurred. For detailed stack trace, please see the page's source code.
Illegal mix of collations (latin5_turkish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='

what should I do to prevent this error ? I need this encoding because of turkish characters..

Thanks

e-mail:ugursamuk@yahoo.com

Anonymous wrote:An error has ocurred. For detailed stack trace, please see the page's source code.
Illegal mix of collations (latin5_turkish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='

what should I do to prevent this error ? I need this encoding because of turkish characters..

Thanks

e-mail:ugursamuk@yahoo.com

You can not use both. utf-8 includes all turkish characters. You no not need latin5_turkish when you use utf-8. Modern web browsers work with utf8 without a problem. But some (old ones) web browsers either do not understand utf8 or have bugs in utf8 implementation. In this case you will see some garbage posted.

Basically utf8 is a modern way to go. The biggest advantage of utf8 compared to all latin5_turkish and etc. is that you can SIMULTANEOUSLY use turkish, greek, chinese, hebrew and any other characters from utf8.

But if your users use outdated web browsers and you need only turkish - then latin5_turkish may be the way to go.

I have tried EVERY suggestion on this list, including even reloading the DB with the UTF8 as the default characterset. I still see the collation error!

I have upgraded to 5.0 on mysql, is this the problem?

It ended up being the 'jforum-custom.conf' file.

there is a property to specify the encoding character set of the DB and another property to set the collation character set (for example: mysqld --default-character-set=latin1 --default-collation=latin1_swedish_ci

i am just now in the process of migrating to 4.1 from 4.0 and there is a lot of difference regarding the DB itself due to the new character support.

for example, of you use UTF-8 characters in 4.0 (which does not nativly support UTF-

you need to go coulumn by column and apply a UTF-8 character set to that column (in order to convert the data inside it).

setting the DB character set to UTF8 will not help in that case.

rafael, i did not go though the jforum instructions for some time now (i use 2.0.2), is there a specific part for dealing with mysql 4.1.x?

thanks

rafael;
in the installation instructions it states:
" Also for MySQL 4.1+ users, go to WEB-INF/config/database/mysql and rename the file "mysql_41.sql" to "mysql.sql" (delete the existing mysql.sql file, which does not work for MySQL 4.1+) "

can you please explain this? what should i do with 2.0.2 and 4.1? should i take the mysql_41.sql from 2.1 and put in 2.0.2? will it work?
thanks in advance.

JForum 2.0.2? I have no idea how files from 2.1 will work with it.

Rafael

are you saying jforum 2.0.2 cannot work with mysql 4.1?

I guess most features will work, but you will have problems when setting permissions for groups.

Rafael

thanks;
well, i do not intend to use this feature. i use jforum for the bare minimum of a plain forum (i am the only admin and i stipped most capabilities that are not a part of the "forum basics").

so my question remains, in the 2.1.x installation there is a special file for mysql 4.1.x users that contains some SQL statements. the installation instructions state that there is a need to replace the regular mysql file with the 4.1 one.

if i want to use 2.0.2 and 4.1 should i also take that specific file and use it or not?

thanks for the help.

You can give it a try!

Rafael