unknown column 'status' [#361228]

Just reporting here that I'm instaling the dev snapshot, as recommended by the maintaner of simplenews, as the solution to an issue I reported regarding simplenews + i18n.

When I switched from 6.x-1.0-beta6 to dev snapshot, i got the following warnings + status messages on the update.php?op=results page.

So far, it hasnt affected regular site actions, but also I havent really thoroughly tested "everything" regarding like creation of new nodes or anything. SHOULD I BE WORRIED ABOUT THIS ERROR or CAN WE SAFELY DISREGARD IT?

WARNING messages:

    * user warning: Unknown column 'status' in 'field list' query: UPDATE locales_target SET status = 1 WHERE lid = 3334 in /home/drupal/drupal-6.2/sites/all/modules/i18n/i18nstrings/i18nstrings.module on line 343.
    * user warning: Unknown column 'status' in 'field list' query: UPDATE locales_target SET status = 1 WHERE lid = 3687 in /home/drupal/drupal-6.2/sites/all/modules/i18n/i18nstrings/i18nstrings.module on line 343.
    * user warning: Unknown column 'status' in 'field list' query: UPDATE locales_target SET status = 1 WHERE lid = 3338 in /home/drupal/drupal-6.2/sites/all/modules/i18n/i18nstrings/i18nstrings.module on line 343.
    * user warning: Unknown column 'status' in 'field list' query: UPDATE locales_target SET status = 1 WHERE lid = 3688 in /home/drupal/drupal-6.2/sites/all/modules/i18n/i18nstrings/i18nstrings.module on line 343.

NOTICE messages:

    * Updated string type:blog:title for textgroup nodetype: Title
    * Updated string type:blog:body for textgroup nodetype: Body
    * Created string type:blog:description for text group nodetype: A <em>blog entry</em> is a single post to an online journal, or <em>blog</em>.
    * Updated string type:poll:title for textgroup nodetype: Question
    * Created string type:poll:description for text group nodetype: A <em>poll</em> is a question with a set of possible responses. A <em>poll</em>, once created, automatically provides a simple running count of the number of votes received for each response.
    * Updated string type:forum:title for textgroup nodetype: Subject
    * Updated string type:forum:body for textgroup nodetype: Body
    * Created string type:forum:description for text group nodetype: A <em>forum topic</em> is the initial post to a new discussion thread within a forum.
    * Updated string type:news:title for textgroup nodetype: Title
    * Updated string type:news:body for textgroup nodetype: Body
    * Created string type:news:description for text group nodetype: A <em>news item</em> is like a site-wide blog post entry. It it used to add info to the homepage about news and events.
    * Updated string type:page:title for textgroup nodetype: Title
    * Updated string type:page:body for textgroup nodetype: Body
    * Created string type:page:description for text group nodetype: A <em>page</em>, similar in form to a <em>story</em>, is a simple method for creating and displaying information that rarely changes, such as an "About us" section of a website. By default, a <em>page</em> entry does not allow visitor comments and is not featured on the site's initial home page.
    * Created string type:simplenews:body for text group nodetype: Body
    * Created string type:simplenews:description for text group nodetype: A newsletter issue to be sent to subscribed email addresses.
    * Created string type:story:title for text group nodetype: Title
    * Created string type:story:body for text group nodetype: Body
    * Created string type:story:description for text group nodetype: A <em>story</em>, similar in form to a <em>page</em>, is ideal for creating and displaying content that informs or engages website visitors. Press releases, site announcements, and informal blog-like entries may all be created with a <em>story</em> entry. By default, a <em>story</em> entry is automatically featured on the site's initial home page, and provides the ability to post comments.

The following queries were executed

i18ncontent module
Update #6001

    * UPDATE {locales_source} SET location = CONCAT('type:', location) WHERE textgroup = 'nodetype' AND location NOT LIKE 'type:%'
    * DELETE FROM {i18n_strings} WHERE lid IN (SELECT lid FROM {locales_source} WHERE textgroup = 'nodetype')

i18nstrings module
Update #6002

    * ALTER TABLE {locales_source} ADD INDEX textgroup_location (textgroup(30), location)

Update #6003

    * ALTER TABLE {locales_target} ADD `status` INT NOT NULL DEFAULT 0

Comments

Comment #1

nedjo

he/him/his

English

CreditAttribution: nedjo commented 20 January 2009 at 05:27

Issue tags:

+i18n sprint

What happened is that some queries were run before the update query that adds a field to locales_target.

Yes, you can safely ignore these messages.

But we need to fix this. It's a case of update.php not respecting dependencies. Really it should update required modules before the modules that depend on them.

Since that's not the case, we need to tweak the code called on install.

The problem seems to be in i18ncontent judging from the messages above.

Comment #2

Jose Reyero CreditAttribution: Jose Reyero commented 21 January 2009 at 12:13

Yes, I think this may be an issue for Drupal core too.

In the meanwhile, let's try to find some fix. Will tweaking module weights fix all these issues?

Comment #3

Jose Reyero CreditAttribution: Jose Reyero commented 21 January 2009 at 13:16

I've done some more research and it seems the orden of the updates is independent of node weight
See:
- update_script_selection_form()
- drupal_get_installed_schema_version()

So this may be more difficult to fix than that...