The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.When I export a node as node code, delete that node from the site and finally re-import it into the same site, I get errors like this every time you re-save the node:
Duplicate entry '1076' for key 'PRIMARY' query: INSERT INTO uuid_node_revisions (vid, uuid) VALUES (1076, 'cae34d4e-47ef-11e1-a6af-5404a6675bac') in /etc/drupal6/all/modules/uuid/uuid.module on line 65.
So it has something to do with the new dependeny - the UUID (Universally Unique IDentifier) module. Why is it required at all if you only enable the main Node export module but none of its sub modules? There was no such dependency in 6.x-2.24.
Comments
Comment #1
danielb commentedWhich version of UUID?
A lot of those sub modules really should be packaged into the main module. UUID is important to exported content, and it is best if any exported content has a UUID attached.
Comment #2
roball commentedI am using the latest release of UUID for D6, which is currently 6.x-1.0-beta2.
Comment #3
danielb commented6.x-1.0-beta2 was released 2010-Sep-08
It wasn't until February 2011 that this issue was fixed: #895622: user warning: Duplicate entry in uuid_node_revisions
I'd say give the dev version a crack, the UUID guy has been a bit slack with releases unfortunately. That is somewhat holding back our commitment to the UUID module, but it is what was recommended to me by several members of the community, I've even been to a damn lecture about the thing, and it is the most 'Drupal' way to create a unique ID for a node as of Drupal 6 and 7.
Comment #4
roball commentedI see and also recognized the bug still existing in UUID 6.x-1.0-beta2. However, don't want to rely on a dev snapshot on production sites. Node export 6.x-3.x is final, but the dependent module UUID 6.x isn't - that's kind of an suboptimal combination. Would you consider removing the dependency of node_export.module to uuid.module, at least until there is a final release of UUID?
Comment #5
danielb commentedI suppose, let me think about it. I'd much prefer the UUID stuff was solved, even if they release it'll still only be a beta.
Comment #6
danielb commented#1417412: Releases, commits, and bug maintenance?
http://drupal.org/node/1256888#comment-5251448
Comment #7
rmcom commentedI consistently get these two error messages since I updated to the latest version:
query: INSERT INTO uuid_node_revisions (vid, uuid) VALUES (97, '7b856a94-434b-4294-0db6-f4db7d266ca9') in /var/www/sites/all/modules/contrib/uuid/uuid.module on line 65.
pg_query(): Query failed: ERROR: duplicate key value violates unique constraint "uuid_node_revisions_pkey" in /var/www/includes/database.pgsql.inc on line 138.
Comment #8
danielb commentedI don't even...
Comment #9
danielb commentedWell no answer on that other issue I made in the UUID queue.
I've removed the UUID dependency from the main UUID module and moved it to the modules that currently use it.
I will also update the project page.
Comment #10
roball commentedThank you for releasing 6.x-3.2 with the removed dependency!
Comment #11
danielb commentedI notice a lot of activity tonight in the UUID issue queue!
http://drupal.org/project/issues/uuid
Comment #13
roball commentedWell, Node export 6.x-3.2 and 6.x-3.3 did NOT depend on Uuid, which is officially still at the (buggy) v6.x-1.0-beta2, but Node export 6.x-3.4 suddenly again depends on it, due to the commit "Backport of handling imports when node already exists.". Why?
Comment #14
danielb commentedThis module must use UUID to uniquely identify nodes for that functionality to work, which in turn clears up a lot of confusion/problems with what is expected from Node export, which came up in other issues.
Feel free to use the previous release of this module if that is unacceptable to you. I'm not going to remove the functionality only to write it back in when they make another release. I refuse to keep going backwards with this module.