database query error when extra languages are added into database

I am adding more languages to my #!Language database. However, when I reach 65th entry and click Save - I get a Database Query Error.

 

In MySQL I have changed ENUM to VARCHAR but that did not resolve the problem. #!Country,for example has a lot more entries and has VARCHAR set in MySQL and it works fine, so I do not understand why the error  gives me: Too many strings for column Languages and SET. This is whatI get in me email:

 

Query:

ALTER TABLE `Profiles` CHANGE `Languages` `Languages` set('10', '20', '30', '40', '50', '60', '70', '80', '90', '100', '110', '120', '130', '140', '150', '160', '170', '180', '190', '200', '210', '220', '230', '240', '250', '260', '270', '280', '290', '300', '310', '320', '330', '340', '350', '360', '370', '380', '390', '400', '410', '420', '430', '440', '450', '460', '470', '480', '490', '500', '510', '520', '530', '540', '550', '560', '570', '580', '590', '600', '610', '620', '630', '640', '650') NOT NULL default ''

Mysql error: Too many strings for column Languages and SET

Found error in the file '/home/www/s2723/public_html/xxxxxxx.com/administration/preValues.php' at line 364.
Called 'db_res' function with erroneous argument #0.

 

Please help me to resolve the issue. I need to add at least another 20 languages.

Quote · 11 Oct 2011

anyone?

Quote · 12 Oct 2011

dont know if this will help you or not, but seems caltrade a unity member here had the same problem:

 

http://www.boonex.com/n/Help_Too_many_items_in_profile_field_SQL_issue

 

~4 years ago. 

 

so there seems to be a sql limitation from this persons explanation 

When a GIG is not enough --> Terabyte Dolphin Technical Support - Server Management and Support
Quote · 12 Oct 2011

It's a SET type, it has a limit of 64 elements. There is no way to get around this limitation without making a lot of other changes to dolphin.

You can't just switch it to a varchar or blob or anything else, there is no comparable type to SET. Probably you'd have to break it into a second SET, and make the code compare against both of them.

 probably best off just not trying to use more than 64 languages.

 

so, this is actually a bug written into dolphin, though not many would find it. when caltrade reported it ~~4 years ago, he was ignored. 

 

kinda the way skyforum is ignored about his issue with the mail system on dolphin. 

When a GIG is not enough --> Terabyte Dolphin Technical Support - Server Management and Support
Quote · 12 Oct 2011

Yes, this is to do with SET which limits the entries to 64.

However, in Predefined Values - Country - there are a lot more entries than 64. So it is possible to get this done. Why did Boonex left out Language with SET?

I hear what you saying about simply cutting the number of languages to 64. This is probably the only valid option at this stage. But not optimal when there are at least 85 languages and your website is global.

Boonex should really stop using SET for predefined values. It does no justice.

Quote · 13 Oct 2011

 that was why i posted the answer. this is an oversight, and most likely needs to be added to trac so this can be fixed. they used the wrong type here it would appear. 

Yes, this is to do with SET which limits the entries to 64.

However, in Predefined Values - Country - there are a lot more entries than 64. So it is possible to get this done. Why did Boonex left out Language with SET?

I hear what you saying about simply cutting the number of languages to 64. This is probably the only valid option at this stage. But not optimal when there are at least 85 languages and your website is global.

Boonex should really stop using SET for predefined values. It does no justice.

 

When a GIG is not enough --> Terabyte Dolphin Technical Support - Server Management and Support
Quote · 13 Oct 2011
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.