This is a pretty serious bug, as it causes nodes to become inaccessible via a "Page Not Found" page, however those nodes still appear in node lists. There is no way to delete the node. Not even using the node_delete() function will work. This is because node_delete() can only delete that which can be loaded with node_load() and these cannot.
To reproduce the error you need pgsql, and create a new content type, and enable the book module. Remove the 'body' field from the content type you created via the settings, and turn on revisions.
Create a node of this new content type which is also a new book. It will absolutely shit itself with pgsql errors regarding body not null constraints, and then you will never be able to edit/delete/view the node, despite it showing up in book hierarchies, content lists, etc... If you select the data out of the {node} table corresponding to the nid in question, you will see that there is insufficient data in the row to join {node_revisions}.
Comments
Comment #1
dpearcefl CreditAttribution: dpearcefl commentedIs this issue still occurring in the current version of Drupal v6?
Comment #2
dpearcefl CreditAttribution: dpearcefl commented