Closed (fixed)
Project:
Nodewords: D6 Meta Tags
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Dec 2009 at 05:03 UTC
Updated:
6 Mar 2010 at 14:50 UTC
While updatong with last version : 6.x-1.x-dev (2009-Dec-15)
I have this error :
user warning:
Duplicate entry '5-597-abstract' for key 2 query: update_sql /* drupaladmin : update_sql */ UPDATE nodewords SET type = 5 WHERE type = 'node' in /home/drupal/drupal/sites/all/modules/nodewords/nodewords.install on line 1215.
Update #6160
Failed: UPDATE {nodewords} SET type = 5 WHERE type = 'node'
Comments
Comment #1
avpadernoI installed version 6.x-1.8 (which has been created before December 25), I changed the meta tags of some nodes, and copied the latest development snapshot (the one without an archive available, yet); I ran update.php (which caused the update functions from #6159 to be executed), but I didn't get any error from the update functions.
From which version did you update?
Comment #2
srobert72 commentedFrom just previous 6.x-1.x-dev (I suppose 2009-Dec-14).
I update everydays.
Comment #3
avpadernoExecuting the update from version 6.x-1.8 didn't cause any error; I am not sure if this means the problem has been resolved.
Which database engine are you using? I had to once change the update functions to make them compatible with PostgreSQL. Are you using that database engine?
Comment #4
avpadernoUhmmm...
Comment #5
srobert72 commentedI use MySQL 5 on Ubuntu server.
When I had this issue (on 2009-Dec-15) , my previous version wasn't 1.8 but previous DEV version from the day before (2009-Dec-14).
Comment #6
avpadernoThat is the only way I had to test update #6160; it is not possible to download a previous release of a development snapshot, so I had to use an official release released before that update function was added. That doesn't change the result, anyway, as long as the update function is executed.
Comment #7
srobert72 commentedYes I think this issue could be closed.
Comment #8
avpadernoI am marking this report as fixed as per previous commit.