| Author |
Message |
warden


Joined: Dec 16, 2004 Posts: 196 Location: North Carolina
|
|
| Back to top |
|
 |
Phoenix


Joined: Apr 19, 2004 Posts: 8729 Location: Netizen
|
Post subject: Re: Column 'filename' cannot be part of FULLTEXT index Posted: Wed Jun 24, 2009 10:38 pm |
|
It means you have mixed collations in your table(s) and may also encounter further issues.
"fulltext" is the type used by the "search" index.
_________________ • DonationsPro for DragonflyCMS, SMF, MyBB, vBulletin •
Phoenix's server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS)
 |
|
| Back to top |
|
 |
warden


Joined: Dec 16, 2004 Posts: 196 Location: North Carolina
|
Post subject: Re: [solved] Column 'filename' cannot be part of FULLTEXT index Posted: Thu Jun 25, 2009 3:11 pm |
|
Thanks Phoenix.
Is there any way to repair the db or work around this? I noticed that the colums are latin1_swedish and the table collations are ut8f_general_ci. Does this have anything to do with the issue?
_________________

warden's server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS)
 |
|
| Back to top |
|
 |
warden


Joined: Dec 16, 2004 Posts: 196 Location: North Carolina
|
Post subject: Re: [solved] Column 'filename' cannot be part of FULLTEXT i Posted: Thu Jun 25, 2009 5:14 pm |
|
I did not solve it, but I did find a workaround.
I have a virtual machine (virtualbox) with a LAMP stack configured. I exported the same DF v.9.1.2 database into the vm phpmyadmin, then went through the db upgrade. Once exported from the vm phpmyadmin, it imported fine within the commercial phpmyadmin on a shared hosting server.
_________________

warden's server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS)
 |
|
| Back to top |
|
 |
layingback


Joined: Apr 19, 2004 Posts: 952
|
Post subject: Re: [solved] Column 'filename' cannot be part of FULLTEXT index Posted: Fri Jun 26, 2009 6:18 am |
|
Sooner or later you will have to fix it, as it will keep comimg back to bite you.
The collations need to be set to ut8f_general_ci (the actual data is already utf8).
Do a search on collations for lots of help. It's in the wiki too.
_________________ Pro_News: The complete module for Dragonfly - now available as version 3.3
layingback's server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS) 2.6 - 3.6 / 1.3.42 - 2.2.12 / 5.0.92 - 5.1.37 - 5.1.54 / 4.4.49 - 5.2.17 - 5.3 / 9.2.1 |
|
| Back to top |
|
 |
rlgura


Joined: Mar 27, 2006 Posts: 1148 Location: Cleveland, OH USA
|
Post subject: Re: [solved] Column 'filename' cannot be part of FULLTEXT index Posted: Fri Jun 26, 2009 4:36 pm |
|
the export/import/export/import Warden did may have straightened up the collation issue. What I normally do for that problem is export the db, open the sql export file in a good text editor and do a find/replace for the collation (changing latin1_swedish to ut8f_general_ci), then re-import the data into a clean db (with default collation set to ut8f_general_ci).
Sounds like a lot of work, but it's actually pretty quick...
_________________ Admin - Great Lakes Web Designs
Theme Designer - WebSite Guru Designs
Site Admin - Families with Food Allergies
rlgura's server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS) Linux 2.6.27-grsec/Apache 2.2.11/MySQL 5.0.67-community-log/PHP 5.2.8/DF 9.2.1 |
|
| Back to top |
|
 |
layingback


Joined: Apr 19, 2004 Posts: 952
|
Post subject: Re: [solved] Column 'filename' cannot be part of FULLTEXT index Posted: Fri Jun 26, 2009 5:58 pm |
|
Good thought!
_________________ Pro_News: The complete module for Dragonfly - now available as version 3.3
layingback's server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS) 2.6 - 3.6 / 1.3.42 - 2.2.12 / 5.0.92 - 5.1.37 - 5.1.54 / 4.4.49 - 5.2.17 - 5.3 / 9.2.1 |
|
| Back to top |
|
 |
warden


Joined: Dec 16, 2004 Posts: 196 Location: North Carolina
|
Post subject: Re: [solved] Column 'filename' cannot be part of FULLTEXT index Posted: Fri Jun 26, 2009 10:41 pm |
|
Thanks for the info guys. I know the collation stuff is not easy to grasp, but I will be a tester to see how it works out. This is an older db that was originally created in 8.2c, then upgraded to 9.0.6.1 and then 9.1.2. There was a big collation issue between 9061 and 912, and I used rlgura's method above to straighten it out so that it would upgrade. I had forgotten about that method. It is a time saver!
Thanks again.
_________________

warden's server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS)
 |
|
| Back to top |
|
 |