I am having problems with adding nodes from SQL. I have added about 1000 nodes with SQL queries that update the node and node_revisions tables (and some CCK tables too). From the looks of it, all the node IDs are sequential. Everything imported successfully, but the only problem I have is when I want to add a new node. The new node has an ID of the beginning node that I imported. In other words, if I imported nodes 100-900 via SQL, when I add a new node through Drupal, that new node ID is 100. This new node does not overwrite the existing data, nor does the new node exist anywhere in the database tables. Rather, the information from the new node is lost or not saved anywhere. After adding that new node unsuccessfully, I tried again and the same thing happened except the ID of the new node was 101 that time, and it increments each time, but it does not save any of the new data.
If I keep incrementing until 901 (the first real new node), I wonder if it will work then. But my real question is: is there a way to tell Drupal to add new nodes at the end (at 901) instead of at 100 or so?
I tried emptying caches to see if that would fix the problem, but that did not seem to. When adding a new node, I assumed Drupal would look in the node table to get the next node ID number. How does it get the next node ID number?
Can anyone think of a fix for this?