By Zen on

It seems that a number of people are using the album module and other modules that use the folksonomy module. I for one can't get the folksonomy module up due to MySQL spitting out errors at me. Creating the folksonomy table as per:

CREATE TABLE `folksonomy` (
  `id` int(11) NOT NULL default '0',
  `realm` varchar(100) NOT NULL default '',
  `name` varchar(255) NOT NULL default '',
  `weight` int(11) NOT NULL default '0',
  PRIMARY KEY  (`id`,`realm`,`name`)
)

results in:

#1071 - Specified key was too long; max key length is 1024 bytes

I've resubmitted the issue as well. But in the meantime if someone knows what's wrong, please let me know. I could get this to work by just omitting "name" as Index, but I'd like to know why this isn't working etc. before using it in a production environment.

Cheers
-K

Comments

Bèr Kessels’s picture

Bèr Kessels commented

In the HEAD development we have folksonomy. his means that ni the next release you will find flksonomy. That is incompqtible with the one you are trying to install.

PLease wait for the next release OR start using head.

---
Next time, please consider filing a support request.

[Bèr Kessels | Drupal services www.webschuur.com]

Zen’s picture

Zen commented

Hi Ber,

Thanks for your reply. I don't think that that's really an attractive option for me. However, will it be ok to install the table without names as an index?

Also, could you please update the modules page with this information? Or remove the module altogether. It's rather misleading..

Cheers
-K

--------
Quillem.com

grohk’s picture

grohk commented

The core folksonomy and the folksonomy modules are not incompatible. Just know that the core folksonomy will probably replace the module in the future and that the album module will need to be changed to accomidate that. But for now they are entirely independent of eachother.

How are you trying to inject the SQL file into the database?

Also, core folksonomy support has been backported to 4.6.0 by Morbus Iff. See his post here: http://drupal.org/node/20936

Zen’s picture

Zen commented

I get the same error if I use PHPMyAdmin or the MySQL CLI on my local windows box running MySQL 4.1.9.

I will have a look at the other link shortly. Thanks :)
-K

--------
Quillem.com

grohk’s picture

grohk commented

I am unable to reproduce on my MySQL 4.1.11 (Mac OSX) or 4.0.17 (GNU/Linux) installs...Perhaps this is a MySQL config problem?

What is you exact environment that you are running?

Also, note that the core folksonomy will not help you use albums, but you could setup your image module gallery to use a free tagging vocabulary.

Zen’s picture

Zen commented

Hi,

I just tested it on my suse box and it worked fine.. weird. I will look into it, cheers :)

-K
--------
Quillem.com

Bèr Kessels’s picture

Bèr Kessels commented

but that depends on the defintion. They will not break one another, but if you have a huge set of folksonomy data build up in the non-core, you will not be able to use that in the core folksonomy in future.

---
Next time, please consider filing a support request.

[Bèr Kessels | Drupal services www.webschuur.com]

grohk’s picture

grohk commented

Point taken Bèr. That is true to the degree...But there are people who will be using the folksonomy module for the next six months or so until 4.7 is released and in the true Drupal way, I hope there will be an upgrade path offered via a script.

For now there are a few 4.6 modules that depend on Moshe's folksonomy and those will not work with Morbus' patch.
---
Code0range: Drink Your Juice

Cromicon’s picture

Cromicon commented

This is a Mysql limitation btw. Using utf8 inflates the character count beyond the mysql limit. I dont know how to resolve but some things Ive seen refer to shortening the index. I dont know how to do this or what effect it has, meanwhile im not using utf8 on that table and it works as far as i can tell.