ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

MySQL Error: 1054

June 17, 2010 3:09pm

Subscribe [4]
  • #1 / Jun 17, 2010 3:09pm

    Jeremy Latham

    74 posts

    I received this error after creating a new weblog & field group and trying to post. Have since deleted the weblog & recreated but still getting the error.

    MySQL ERROR:
    
    Error Number: 1054
    
    Description: Unknown column 'field_id_567' in 'field list'
    
    Query: INSERT INTO `exp_weblog_data` (`entry_id`, `weblog_id`, `field_id_567`, `field_ft_567`, `site_id`) VALUES ('695', '116', 'Test', 'none', '1')

    Can anyone point me in the right direction to fix this?

    EE 1.6.8 Build:  20090723 / MSM 1.1

  • #2 / Jun 17, 2010 3:55pm

    Ingmar

    29245 posts

    There seems to be an inconsistency in your database. Do you have a recent backup? Simply rolling back might be the easiest way to rectify this.

  • #3 / Jun 17, 2010 7:25pm

    Jeremy Latham

    74 posts

    Hi Ingmar - thanks for your reply.

    The most recent backup I have would still entail a fair bit of work to get everything back up to speed - a lot of info spread around a lot of sites, so if there’s a way that I can sort this out without going that route it would make my life a lot easier.

    It appears that I’m getting errors for field_id_567 & field_id_568. It won’t allow me to delete the custom field group that I created. When I try to delete the individual custom fields within that field group, these are the two errors I get.

    MySQL ERROR:
    
    Error Number: 1091
    
    Description: Can't DROP 'field_id_567'; check that column/key exists
    
    Query: ALTER TABLE exp_weblog_data DROP COLUMN field_id_567
    MySQL ERROR:
    
    Error Number: 1091
    
    Description: Can't DROP 'field_id_568'; check that column/key exists
    
    Query: ALTER TABLE exp_weblog_data DROP COLUMN field_id_568

    I’m a total novice when it comes to doing anything more than creating, importing, or exporting databases. But I’ve used EE extensively.

    Any help is much appreciated.

    Thanks

  • #4 / Jun 17, 2010 8:35pm

    Brandon Jones

    5500 posts

    Hi Jeremy,

    Using phpMyAdmin, do an export (backup) of your current database to be safe. Then click on ‘exp_weblog_fields’ on the left, then click the Browse tab at the top. Then click the ‘field_id’ column to sort descending.

    Are there entries with a field_id of 567 and 568?

  • #5 / Jun 17, 2010 8:49pm

    Jeremy Latham

    74 posts

    Yes there are.

  • #6 / Jun 17, 2010 9:38pm

    Brandon Jones

    5500 posts

    OK. You can remove those two entries. Then click on ‘exp_field_groups’ on the left, hit Browse, and you should see the offending field group (the one that won’t delete) in there. Go ahead and remove that as well.

    That *should* get you back to a normal, error-free installation. If so, again do an export of your database at this stage. You may be hitting a column limit of MySQL on your sever. What version of PHP and MySQL are you running?

  • #7 / Jun 17, 2010 10:16pm

    Jeremy Latham

    74 posts

    Thanks Brandon. You’re a star. I managed to delete the entries you instructed me on. DB is backed up again.

    I tried creating new custom fields and ran in to the same problem.

    PHP Version 5.2.13
    MySQL client version: 5.0.77

    Tech Support at Rackspace Cloud tells me that there is no column limit.

    Any ideas on where I can go from here?

    Thanks!

  • #8 / Jun 17, 2010 11:44pm

    Jeremy Latham

    74 posts

    Hey Brandon,

    I found this thread that appears to be covering a similar problem.

    http://ellislab.com/forums/viewthread/152288/P18/

    As I mentioned, I’m really not particularly DB savvy. If I am running up against a limit because of innodb, can I simply toggle the switch for that table to change it to MyISAM?

    Any help is really appreciated!

    Cheers

  • #9 / Jun 18, 2010 12:39am

    John Henry Donovan

    12339 posts

    Jeremy,

    You can run a SQL query in phpMyAdmin like the following. Just substitute your table_name each time.

    ALTER TABLE table_name ENGINE=MYISAM

    Back up db beforehand if you have not done so already.

  • #10 / Jun 21, 2010 3:39pm

    Jeremy Latham

    74 posts

    Switching the exp_weblog_data table to MyISAM seems to have fixed the problem, as in Boyink’s thread about a similar issue.

    Is there any long term issue having InnoDB for all the other tables and MyISAM for the exp_weblog_data table?

    Thanks for all the help you guys!

  • #11 / Jun 21, 2010 4:02pm

    Ingmar

    29245 posts

    I am not aware of any. If it works, don’t worry about it.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases