Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Wikipedia: Mediawiki

Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations

 

 

Wikipedia mediawiki RSS feed   Index | Next | Previous | View Threaded


ek79501 at yahoo

Aug 23, 2008, 9:30 AM

Post #1 of 8 (498 views)
Permalink
Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations

Everything works on my wiki, except when I view the logs for a page, I get this error:

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "LinkCache::addLinkObj". MySQL returned error "1267: Illegal mix of collations (latin1_bin,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' (localhost)".
Any ideas on how to fix this? I can go into myPhPAdmin and manipulate tables if needed.
 
thanks
Eric



_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l


ek79501 at yahoo

Aug 25, 2008, 6:27 PM

Post #2 of 8 (466 views)
Permalink
Re: Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations [In reply to]

Here's what I found. When Mediawiki upgrades, it doesnt seem to care to update the table schemes properly. Here's a sample of what I found:
 
Old table row specs, for mw_image (this is after the upgrade has been applied from 1.9.3 to 1.13.0):
img_size int(8)
img_width int(5)
img_height int(5)
 
New table row specs for the same table, mw_image (for a brand new 1.13.0 installation):
img_size int(10)
img_width int(11)
img_height int(11)
 
The field sizes are different as you can see. New tables have bigger fields but the old ones still contain short fields after the upgrade is applied.This is just an example. The bug that I was getting (illegal mix of collations), was fixed due to the Collation fields being different in the cases for an upgraded MW and a new MW. I also noticed differences in all the other fields as well (Default, Type, Binary, Attributes) for tables rows. Sometimes the differences were significant. Here are some real examples:
- length of data field doubled for example, int(5) to int (10)
- the Type changed in an upgraded version from "varbinary(255)" to "blob", in a new installation
 
Usually, Collate was empty for a brand new 1.13.0, while it was latin_bin or latin1_swedish_ci for an upgraded version.
 
There must be important reasons why changes were made to the rows as versions progressed.
 
So i guess this is something that should be fixed for upgrading? That means, when an upgrade is being applied, it should update all the row data for each table as well.
 
Erik
 


--- On Sat, 8/23/08, Eric K <ek79501[at]yahoo.com> wrote:

From: Eric K <ek79501[at]yahoo.com>
Subject: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations
To: mediawiki-l[at]lists.wikimedia.org
Date: Saturday, August 23, 2008, 11:30 AM

Everything works on my wiki, except when I view the logs for a page, I get this
error:

A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:
(SQL query hidden)
from within function "LinkCache::addLinkObj". MySQL returned error
"1267: Illegal mix of collations (latin1_bin,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '=' (localhost)".
Any ideas on how to fix this? I can go into myPhPAdmin and manipulate tables if
needed.
 
thanks
Eric



_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l




_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l


sullivan at mail

Aug 26, 2008, 4:44 AM

Post #3 of 8 (462 views)
Permalink
Re: Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix of collations [In reply to]

After upgrading the Mediawiki code did you run:
maintenance/update.php
and
maintenance/refreshLinks.php
?

-Jim


-----Original Message-----
From: Eric K [mailto:ek79501[at]yahoo.com]
Sent: Monday, August 25, 2008 9:27 PM
To: mediawiki-l[at]lists.wikimedia.org
Subject: Re: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix of collations

Here's what I found. When Mediawiki upgrades, it doesnt seem to care to update the table schemes properly. Here's a sample of what I found:
 
Old table row specs, for mw_image (this is after the upgrade has been applied from 1.9.3 to 1.13.0):
img_size int(8)
img_width int(5)
img_height int(5)
 
New table row specs for the same table, mw_image (for a brand new 1.13.0 installation):
img_size int(10)
img_width int(11)
img_height int(11)
 
The field sizes are different as you can see. New tables have bigger fields but the old ones still contain short fields after the upgrade is applied.This is just an example. The bug that I was getting (illegal mix of collations), was fixed due to the Collation fields being different in the cases for an upgraded MW and a new MW. I also noticed differences in all the other fields as well (Default, Type, Binary, Attributes) for tables rows. Sometimes the differences were significant. Here are some real examples:
- length of data field doubled for example, int(5) to int (10)
- the Type changed in an upgraded version from "varbinary(255)" to "blob", in a new installation
 
Usually, Collate was empty for a brand new 1.13.0, while it was latin_bin or latin1_swedish_ci for an upgraded version.
 
There must be important reasons why changes were made to the rows as versions progressed.
 
So i guess this is something that should be fixed for upgrading? That means, when an upgrade is being applied, it should update all the row data for each table as well.
 
Erik
 


--- On Sat, 8/23/08, Eric K <ek79501[at]yahoo.com> wrote:

From: Eric K <ek79501[at]yahoo.com>
Subject: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations
To: mediawiki-l[at]lists.wikimedia.org
Date: Saturday, August 23, 2008, 11:30 AM

Everything works on my wiki, except when I view the logs for a page, I get this
error:

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "LinkCache::addLinkObj". MySQL returned error
"1267: Illegal mix of collations (latin1_bin,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '=' (localhost)".
Any ideas on how to fix this? I can go into myPhPAdmin and manipulate tables if needed.
 
thanks
Eric



_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l




_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l


ek79501 at yahoo

Aug 26, 2008, 5:20 AM

Post #4 of 8 (463 views)
Permalink
Re: Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix of collations [In reply to]

[sorry for the duplicate message, forgot to CC to the list]
 
That might be it but, the directions dont ask me to run those scripts separately, as far as I can see?
http://www.mediawiki.org/wiki/Manual:Upgrading_MediaWiki
 
I followed the Alternative 2, which just asked me to re-run the installer. In that, it says:
- "When the installation process starts, the script will detect existing MediaWiki tables, and upgrade their schema."
 
 

--- On Tue, 8/26/08, Eric K <ek79501[at]yahoo.com> wrote:

From: Eric K <ek79501[at]yahoo.com>
Subject: RE: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix of collations
To: "Sullivan, James (NIH/CIT) [C]" <sullivan[at]mail.nih.gov>
Date: Tuesday, August 26, 2008, 7:19 AM







That might be it but, the directions dont ask me to run those scripts separately, as far as I can see?
http://www.mediawiki.org/wiki/Manual:Upgrading_MediaWiki
 
I followed the Alternative 2, which just asked me to re-run the installer. In that, it says:
- "When the installation process starts, the script will detect existing MediaWiki tables, and upgrade their schema."
 
hmmm.


--- On Tue, 8/26/08, Sullivan, James (NIH/CIT) [C] <sullivan[at]mail.nih.gov> wrote:

From: Sullivan, James (NIH/CIT) [C] <sullivan[at]mail.nih.gov>
Subject: RE: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix of collations
To: ek79501[at]yahoo.com, "MediaWiki announcements and site admin list" <mediawiki-l[at]lists.wikimedia.org>
Date: Tuesday, August 26, 2008, 6:44 AM

After upgrading the Mediawiki code did you run:
maintenance/update.php
and
maintenance/refreshLinks.php
?

-Jim


-----Original Message-----
From: Eric K [mailto:ek79501[at]yahoo.com]
Sent: Monday, August 25, 2008 9:27 PM
To: mediawiki-l[at]lists.wikimedia.org
Subject: Re: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix
of collations

Here's what I found. When Mediawiki upgrades, it doesnt seem to care to
update the table schemes properly. Here's a sample of what I found:
 
Old table row specs, for mw_image (this is after the upgrade has been applied
from 1.9.3 to 1.13.0):
img_size int(8)
img_width int(5)
img_height int(5)
 
New table row specs for the same table, mw_image (for a brand new 1.13.0
installation):
img_size int(10)
img_width int(11)
img_height int(11)
 
The field sizes are different as you can see. New tables have bigger fields but
the old ones still contain short fields after the upgrade is applied.This is
just an example. The bug that I was getting (illegal mix of collations), was
fixed due to the Collation fields being different in the cases for an upgraded
MW and a new MW. I also noticed differences in all the other fields as well
(Default, Type, Binary, Attributes) for tables rows. Sometimes the differences
were significant. Here are some real examples:
- length of data field doubled for example, int(5) to int (10)
- the Type changed in an upgraded version from "varbinary(255)" to
"blob", in a new installation
 
Usually, Collate was empty for a brand new 1.13.0, while it was latin_bin or
latin1_swedish_ci for an upgraded version.
 
There must be important reasons why changes were made to the rows as versions
progressed.
 
So i guess this is something that should be fixed for upgrading? That means,
when an upgrade is being applied, it should update all the row data for each
table as well.
 
Erik
 


--- On Sat, 8/23/08, Eric K <ek79501[at]yahoo.com> wrote:

From: Eric K <ek79501[at]yahoo.com>
Subject: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of
collations
To: mediawiki-l[at]lists.wikimedia.org
Date: Saturday, August 23, 2008, 11:30 AM

Everything works on my wiki, except when I view the logs for a page, I get this
error:

A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:
(SQL query hidden)
from within function "LinkCache::addLinkObj". MySQL returned error
"1267: Illegal mix of collations (latin1_bin,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '=' (localhost)".
Any ideas on how to fix this? I can go into myPhPAdmin and manipulate tables if
needed.
 
thanks
Eric



_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l




_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l





_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l


sullivan at mail

Aug 26, 2008, 5:32 AM

Post #5 of 8 (463 views)
Permalink
Re: Upgraded from 1.9.3 to 1.13.0- got error:Illegalmix of collations [In reply to]

Assuming Alternative 2 works as advertised, check that permissions are set properly and that it ran completely. I've always used the commandline method so I'm not familiar with Alternative 2.

Also, consider that an extension that is working with the old schema needs to be upgraded.

And if you have commandline access, try running update.php from the commandline.

If that fails you may want to start from scratch and do the upgrade again from backups.

-Jim

-----Original Message-----
From: Eric K [mailto:ek79501[at]yahoo.com]
Sent: Tuesday, August 26, 2008 8:21 AM
To: mediawiki-l[at]lists.wikimedia.org
Subject: Re: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error:Illegalmix of collations






[sorry for the duplicate message, forgot to CC to the list]
 
That might be it but, the directions dont ask me to run those scripts separately, as far as I can see?
http://www.mediawiki.org/wiki/Manual:Upgrading_MediaWiki
 
I followed the Alternative 2, which just asked me to re-run the installer. In that, it says:
- "When the installation process starts, the script will detect existing MediaWiki tables, and upgrade their schema."
 
 

--- On Tue, 8/26/08, Eric K <ek79501[at]yahoo.com> wrote:

From: Eric K <ek79501[at]yahoo.com>
Subject: RE: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix of collations
To: "Sullivan, James (NIH/CIT) [C]" <sullivan[at]mail.nih.gov>
Date: Tuesday, August 26, 2008, 7:19 AM







That might be it but, the directions dont ask me to run those scripts separately, as far as I can see?
http://www.mediawiki.org/wiki/Manual:Upgrading_MediaWiki
 
I followed the Alternative 2, which just asked me to re-run the installer. In that, it says:
- "When the installation process starts, the script will detect existing MediaWiki tables, and upgrade their schema."
 
hmmm.


--- On Tue, 8/26/08, Sullivan, James (NIH/CIT) [C] <sullivan[at]mail.nih.gov> wrote:

From: Sullivan, James (NIH/CIT) [C] <sullivan[at]mail.nih.gov>
Subject: RE: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix of collations
To: ek79501[at]yahoo.com, "MediaWiki announcements and site admin list" <mediawiki-l[at]lists.wikimedia.org>
Date: Tuesday, August 26, 2008, 6:44 AM

After upgrading the Mediawiki code did you run:
maintenance/update.php
and
maintenance/refreshLinks.php
?

-Jim


-----Original Message-----
From: Eric K [mailto:ek79501[at]yahoo.com]
Sent: Monday, August 25, 2008 9:27 PM
To: mediawiki-l[at]lists.wikimedia.org
Subject: Re: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix of collations

Here's what I found. When Mediawiki upgrades, it doesnt seem to care to update the table schemes properly. Here's a sample of what I found:
 
Old table row specs, for mw_image (this is after the upgrade has been applied from 1.9.3 to 1.13.0):
img_size int(8)
img_width int(5)
img_height int(5)
 
New table row specs for the same table, mw_image (for a brand new 1.13.0
installation):
img_size int(10)
img_width int(11)
img_height int(11)
 
The field sizes are different as you can see. New tables have bigger fields but the old ones still contain short fields after the upgrade is applied.This is just an example. The bug that I was getting (illegal mix of collations), was fixed due to the Collation fields being different in the cases for an upgraded MW and a new MW. I also noticed differences in all the other fields as well (Default, Type, Binary, Attributes) for tables rows. Sometimes the differences were significant. Here are some real examples:
- length of data field doubled for example, int(5) to int (10)
- the Type changed in an upgraded version from "varbinary(255)" to "blob", in a new installation
 
Usually, Collate was empty for a brand new 1.13.0, while it was latin_bin or latin1_swedish_ci for an upgraded version.
 
There must be important reasons why changes were made to the rows as versions progressed.
 
So i guess this is something that should be fixed for upgrading? That means, when an upgrade is being applied, it should update all the row data for each table as well.
 
Erik
 


--- On Sat, 8/23/08, Eric K <ek79501[at]yahoo.com> wrote:

From: Eric K <ek79501[at]yahoo.com>
Subject: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations
To: mediawiki-l[at]lists.wikimedia.org
Date: Saturday, August 23, 2008, 11:30 AM

Everything works on my wiki, except when I view the logs for a page, I get this
error:

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "LinkCache::addLinkObj". MySQL returned error
"1267: Illegal mix of collations (latin1_bin,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '=' (localhost)".
Any ideas on how to fix this? I can go into myPhPAdmin and manipulate tables if needed.
 
thanks
Eric



_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l




_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l





_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l


brion at wikimedia

Aug 26, 2008, 8:45 AM

Post #6 of 8 (461 views)
Permalink
Re: Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Eric K wrote:
> Here's what I found. When Mediawiki upgrades, it doesnt seem to care to update the table schemes properly. Here's a sample of what I found:
>
> Old table row specs, for mw_image (this is after the upgrade has been applied from 1.9.3 to 1.13.0):
> img_size int(8)
> img_width int(5)
> img_height int(5)

"Sizes" for integer fields are purely imaginary and have no actual
effect. We've generally removed them as they just confuse people.

> Usually, Collate was empty for a brand new 1.13.0, while it was
> latin_bin or latin1_swedish_ci for an upgraded version.

Can you provide details of the original schema collation and what MySQL
version and schema mode options were in use in your old *and* your new
LocalSettings.php?

The 1.13 updater should be configuring things properly for your database
(but older updaters *did not* always do this correctly).

- -- brion
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAki0JREACgkQwRnhpk1wk45g2wCfVY0t/W2pAUwXUxiUTDPYEn9p
+HQAnj4jtYeYg72FUmDoA8uyW9ua+zeE
=DZmJ
-----END PGP SIGNATURE-----

_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l


ek79501 at yahoo

Aug 27, 2008, 6:02 PM

Post #7 of 8 (441 views)
Permalink
Re: Upgraded from 1.9.3 to 1.13.0- got error:Illegalmix of collations [In reply to]

Hi Jim, thanks. There were some problems during installation but it did go through. Since I was able to change the table structures by hand, I assumed the script could have done the same but did not. In my next upgrade, I will take notes and compare the schemas and then get back here if I notice differences.
thanks!
Eric
 


--- On Tue, 8/26/08, Sullivan, James (NIH/CIT) [C] <sullivan[at]mail.nih.gov> wrote:

From: Sullivan, James (NIH/CIT) [C] <sullivan[at]mail.nih.gov>
Subject: RE: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error:Illegalmix of collations
To: ek79501[at]yahoo.com, "MediaWiki announcements and site admin list" <mediawiki-l[at]lists.wikimedia.org>
Date: Tuesday, August 26, 2008, 7:32 AM

Assuming Alternative 2 works as advertised, check that permissions are set
properly and that it ran completely. I've always used the commandline
method so I'm not familiar with Alternative 2.

Also, consider that an extension that is working with the old schema needs to
be upgraded.

And if you have commandline access, try running update.php from the
commandline.

If that fails you may want to start from scratch and do the upgrade again from
backups.

-Jim

-----Original Message-----
From: Eric K [mailto:ek79501[at]yahoo.com]
Sent: Tuesday, August 26, 2008 8:21 AM
To: mediawiki-l[at]lists.wikimedia.org
Subject: Re: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error:Illegalmix
of collations






[sorry for the duplicate message, forgot to CC to the list]
 
That might be it but, the directions dont ask me to run those scripts
separately, as far as I can see?
http://www.mediawiki.org/wiki/Manual:Upgrading_MediaWiki
 
I followed the Alternative 2, which just asked me to re-run the installer. In
that, it says:
- "When the installation process starts, the script will detect existing
MediaWiki tables, and upgrade their schema."
 
 

--- On Tue, 8/26/08, Eric K <ek79501[at]yahoo.com> wrote:

From: Eric K <ek79501[at]yahoo.com>
Subject: RE: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix
of collations
To: "Sullivan, James (NIH/CIT) [C]" <sullivan[at]mail.nih.gov>
Date: Tuesday, August 26, 2008, 7:19 AM







That might be it but, the directions dont ask me to run those scripts
separately, as far as I can see?
http://www.mediawiki.org/wiki/Manual:Upgrading_MediaWiki
 
I followed the Alternative 2, which just asked me to re-run the installer. In
that, it says:
- "When the installation process starts, the script will detect existing
MediaWiki tables, and upgrade their schema."
 
hmmm.


--- On Tue, 8/26/08, Sullivan, James (NIH/CIT) [C]
<sullivan[at]mail.nih.gov> wrote:

From: Sullivan, James (NIH/CIT) [C] <sullivan[at]mail.nih.gov>
Subject: RE: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix
of collations
To: ek79501[at]yahoo.com, "MediaWiki announcements and site admin list"
<mediawiki-l[at]lists.wikimedia.org>
Date: Tuesday, August 26, 2008, 6:44 AM

After upgrading the Mediawiki code did you run:
maintenance/update.php
and
maintenance/refreshLinks.php
?

-Jim


-----Original Message-----
From: Eric K [mailto:ek79501[at]yahoo.com]
Sent: Monday, August 25, 2008 9:27 PM
To: mediawiki-l[at]lists.wikimedia.org
Subject: Re: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegalmix
of collations

Here's what I found. When Mediawiki upgrades, it doesnt seem to care to
update the table schemes properly. Here's a sample of what I found:
 
Old table row specs, for mw_image (this is after the upgrade has been applied
from 1.9.3 to 1.13.0):
img_size int(8)
img_width int(5)
img_height int(5)
 
New table row specs for the same table, mw_image (for a brand new 1.13.0
installation):
img_size int(10)
img_width int(11)
img_height int(11)
 
The field sizes are different as you can see. New tables have bigger fields but
the old ones still contain short fields after the upgrade is applied.This is
just an example. The bug that I was getting (illegal mix of collations), was
fixed due to the Collation fields being different in the cases for an upgraded
MW and a new MW. I also noticed differences in all the other fields as well
(Default, Type, Binary, Attributes) for tables rows. Sometimes the differences
were significant. Here are some real examples:
- length of data field doubled for example, int(5) to int (10)
- the Type changed in an upgraded version from "varbinary(255)" to
"blob", in a new installation
 
Usually, Collate was empty for a brand new 1.13.0, while it was latin_bin or
latin1_swedish_ci for an upgraded version.
 
There must be important reasons why changes were made to the rows as versions
progressed.
 
So i guess this is something that should be fixed for upgrading? That means,
when an upgrade is being applied, it should update all the row data for each
table as well.
 
Erik
 


--- On Sat, 8/23/08, Eric K <ek79501[at]yahoo.com> wrote:

From: Eric K <ek79501[at]yahoo.com>
Subject: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of
collations
To: mediawiki-l[at]lists.wikimedia.org
Date: Saturday, August 23, 2008, 11:30 AM

Everything works on my wiki, except when I view the logs for a page, I get this
error:

A database query syntax error has occurred. This may indicate a bug in the
software. The last attempted database query was:
(SQL query hidden)
from within function "LinkCache::addLinkObj". MySQL returned error
"1267: Illegal mix of collations (latin1_bin,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '=' (localhost)".
Any ideas on how to fix this? I can go into myPhPAdmin and manipulate tables if
needed.
 
thanks
Eric



_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l




_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l





_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l




_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l


ek79501 at yahoo

Aug 27, 2008, 6:04 PM

Post #8 of 8 (441 views)
Permalink
Re: Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations [In reply to]

Hi Brion,
I apologize, I've done the upgrade already, but I will take notes in the next upgrade, follow your directions and will let you know here if I see any differences then.
thanks
Eric
 


--- On Tue, 8/26/08, Brion Vibber <brion[at]wikimedia.org> wrote:

From: Brion Vibber <brion[at]wikimedia.org>
Subject: Re: [Mediawiki-l] Upgraded from 1.9.3 to 1.13.0- got error: Illegal mix of collations
To: ek79501[at]yahoo.com, "MediaWiki announcements and site admin list" <mediawiki-l[at]lists.wikimedia.org>
Date: Tuesday, August 26, 2008, 10:45 AM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Eric K wrote:
> Here's what I found. When Mediawiki upgrades, it doesnt seem to care
to update the table schemes properly. Here's a sample of what I found:
>
> Old table row specs, for mw_image (this is after the upgrade has been
applied from 1.9.3 to 1.13.0):
> img_size int(8)
> img_width int(5)
> img_height int(5)

"Sizes" for integer fields are purely imaginary and have no actual
effect. We've generally removed them as they just confuse people.

> Usually, Collate was empty for a brand new 1.13.0, while it was
> latin_bin or latin1_swedish_ci for an upgraded version.

Can you provide details of the original schema collation and what MySQL
version and schema mode options were in use in your old *and* your new
LocalSettings.php?

The 1.13 updater should be configuring things properly for your database
(but older updaters *did not* always do this correctly).

- -- brion
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAki0JREACgkQwRnhpk1wk45g2wCfVY0t/W2pAUwXUxiUTDPYEn9p
+HQAnj4jtYeYg72FUmDoA8uyW9ua+zeE
=DZmJ
-----END PGP SIGNATURE-----




_______________________________________________
MediaWiki-l mailing list
MediaWiki-l[at]lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Wikipedia mediawiki RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.