Thread

Hello,

One of our EE sites is throwing MySQL errors when saving, deleting, installing an extension or removing an extension. When saving or installing I am getting:

MySQL ERROR:
Error Number: 1030
Description: Got error 139 from storage engine
Query: ALTER TABLE exp_weblog_data ADD COLUMN field_id_220 int(10) NOT NULL

And when deleting or removing I am getting:

MySQL ERROR:
Error Number: 1054
Description: Unknown column ‘field_id_220’ in ‘field list’
Query: SELECT field_id_220 AS rel_id FROM exp_weblog_data WHERE field_id_220 != ‘0’

Any assistance would be greatly appreciated!
Bret

A little bit more research led me to this article:

http://expressionengine.com/knowledge_base/article/how_many_custom_fields_can_my_installation_support/

The site in question does have a ton of custom fields and has had many removed. At current it shows 84 custom fields when I look in the admin panel. When I go into the database and look at exp_weblog_data I see nearly 200 columns labeled field_ft_124 (or whatever number).

Are custom fields not being deleted from the db when they are deleted in the admin panel? If so how can I tell what ones are no longer being used?

Bret

bretjg - while we should figure out the mistmatch, 200 custom fields should not be an issue in 1.6.9. What version and build of EE are you on?  Any extensions?

Thanks for taking the time to respond. It is EE 1.6.8.

Extensions it is currently using:

1. jquery for control panel
2. fieldframe
3. rating
4. edit tab ajax
5. files
6. LG better meta
7. DE Required catalog
8. Calendar
9. Favorites

The site has 22 plugins listed in the plugin manager as well. Any ideas?

Kind Regards,
Bret

I’m not familiar with some of those add-ons, specifically 7.  Are you running your database as MyISAM or InnoDB?

Hi,

The type in on a per table basis. Looks like 2/3 of the tables are InnoDB.

Bret

I don’t believe the quantity of custom fields is an issue. It’s the ‘error 139’ that will need to be diagnosed on your server, as that’s what’s causing the columns to get out of sync.

What version of MySQL are you running? Can you ask your host/server admin about this error?

Thanks All.

MySQL is 5.0. Turns out changing the table storage engine from InnoDB to MySAM resolved the issue. I noticed in a clean install of 1.6.8 all of the tables used MyISAM - since about half my tables are using InnoDB should I change them to match the MyISAM type that the clean install had?

Bret

Is there a particular reason to use InnoDB? Otherwise, yes, I’d use MyMyISAM; certainly so if that actually works.

Honestly I have no idea how they go to be InnoDB. Thanks!

Bret

So, just to confirm, are you up and running? Everything working as it should be?

Correct, I can add and delete now. Thank you very much for checking back in, have a great one!

Bret

Glad you’re back up and running, Bret!