By thesutex on

* user warning: Duplicate entry '8' for key 1 query: INSERT INTO node (nid, vid, title, type, uid, status, created, changed, comment, promote, moderate, sticky) VALUES (8, 8, 'hk', 'blog', 1, 1, 1146009658, 1146009658, 2, 1, 0, 0) in /hsphere/local/home/thesutex/blog.heggli.biz/includes/database.mysql.inc on line 120.
* user warning: Duplicate entry '8' for key 1 query: INSERT INTO node_revisions (nid, vid, title, body, teaser, log, timestamp, uid, format) VALUES (8, 8, 'hk', 'gy', 'gy', '', 1146009658, 1, 3) in /hsphere/local/home/thesutex/blog.heggli.biz/includes/database.mysql.inc on line 120.
* user warning: Duplicate entry '8' for key 1 query: INSERT INTO node_comment_statistics (nid, last_comment_timestamp, last_comment_name, last_comment_uid, comment_count) VALUES (8, 1146009658, NULL, 1, 0) in /hsphere/local/home/thesutex/blog.heggli.biz/includes/database.mysql.inc on line 120.

i upgraded my drupal site to 4.7 and encountered some problems. so i backed up my database and installed a fresh install, where i moved the posts and comments over to the new database. but then it started to add posts in the database with key=1 and so on. trying to overwrite posts that are occupying these key spots if you know what i mean.

as you can see, it started at the top again when creating posts, adding them with nid=1 and so on.. but i have them filled untill 220. How do i tell drupal (or the database) to stop this and start adding posts at nid=221 and so on?

anyone know what to do? =)

thanx!

Comments

slower’s picture

slower commented

Change the `node_nid` field in the `sequences` table to the next available ID number. You might also want to check the other sequences in that table to make sure you won't run into problems with other modules and such.

thesutex’s picture

thesutex commented

thank you very very much :) now i can start to update the blogosphere again =)

JohnR’s picture

JohnR commented

This happens if you change the table prefix. Such as if you move to a multisite installation.