I upgraded my MySQL to 4.1.5 and I was getting " Illegal mix of collations (latin2_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation" in my error log. After a bit of reading, I found out what was the problem, I had to execute 'SET CHARACTER SET latin2' so that the client would change the default character set. I had to modify the module source to make it work. I`m not a C coder, so all I did was a bit of copy/paste. if anyone is interesed, I can provide the changes, and if the maintainer of this project is reading my post, maybe he can change the code in a proper manner, I patched it a bit :) Looks ugly, but it works :)
Alex
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, it looks like a change to MySQL will potentially cause some problems here.
MySQL 4.1.x can have different collations for the installation, database, table and connection. So, just setting latin2 in the code won't work - others may want different collations.
Once MySQL 4.1.x goes into production (it's in gamma right now), we'll have to look into it. We may have to add another option to the module to set the collation.
As for making the changes right now - I don't think so. Pre-release (even gamma) code can change before the final release, and I don't want to make a change now only to have to change it again when the final release comes out.
You might want to enter this in the bug database so we can track it once the final release does come out (forum items are not tracked) and ensure we do get a change in. The bug database also allows you to upload your patch so others may be able to use it.
Jerry
Jerry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the fast answer :) You`re right, adding latin2 won`t to the job for everyone, it worked for me.
I`ll add an entry in the bug database, I`m not sure I should add a patch,
I`ll add the code, and maybe someone who know more about C than I do can write
some proper code for this :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I upgraded my MySQL to 4.1.5 and I was getting " Illegal mix of collations (latin2_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation" in my error log. After a bit of reading, I found out what was the problem, I had to execute 'SET CHARACTER SET latin2' so that the client would change the default character set. I had to modify the module source to make it work. I`m not a C coder, so all I did was a bit of copy/paste. if anyone is interesed, I can provide the changes, and if the maintainer of this project is reading my post, maybe he can change the code in a proper manner, I patched it a bit :) Looks ugly, but it works :)
Alex
Hi, Alex,
Well, it looks like a change to MySQL will potentially cause some problems here.
MySQL 4.1.x can have different collations for the installation, database, table and connection. So, just setting latin2 in the code won't work - others may want different collations.
Once MySQL 4.1.x goes into production (it's in gamma right now), we'll have to look into it. We may have to add another option to the module to set the collation.
As for making the changes right now - I don't think so. Pre-release (even gamma) code can change before the final release, and I don't want to make a change now only to have to change it again when the final release comes out.
You might want to enter this in the bug database so we can track it once the final release does come out (forum items are not tracked) and ensure we do get a change in. The bug database also allows you to upload your patch so others may be able to use it.
Jerry
Jerry
Thanks for the fast answer :) You`re right, adding latin2 won`t to the job for everyone, it worked for me.
I`ll add an entry in the bug database, I`m not sure I should add a patch,
I`ll add the code, and maybe someone who know more about C than I do can write
some proper code for this :)
Hi, Alex,
Thanks for opening the bug report. We'll be looking into the best way to fix this.
Meanwhile, if anyone has any suggestions on how they would like to see this fixed permanently, please post them in the bug report.
Thanks,
Jerry