After creating several panel pages i started recieving the following error, and now i cannot create new panel pages
* user warning: Duplicate entry '19' for key 1 query: INSERT INTO panels_display (did, layout, layout_settings, panel_settings, cache) VALUES (19, 'flexible', 'N;', 'N;', 'N;') in /web/nuvo/includes/database.mysql.inc on line 172.
* user warning: Duplicate entry '15' for key 1 query: INSERT INTO panels_page ( name, title, arguments, displays, contexts, relationships, access, path, css_id, pid, did) VALUES ('edit_image_galleries', 'Image Gallery Management', 'a:0:{}', 'a:0:{}', 'a:0:{}', 'a:0:{}', '', 'admin/editorial/imagegalleries', 'edit-menu', 15, 19) in /web/nuvo/includes/database.mysql.inc on line 172.
Comments
Comment #1
sdboyer commentedThe short-term fix is to go into your sequences table and make sure the panels_page_id and panels_display_id are equal to the largest pid and did that you see in the panels_page and panels_display tables.
However, something you did caused the sequencing to get off track, clearly, and the problem could resurface. However, I need more specific information about what you did leading up to this error for me to begin to be able to track down the source of the problem.
Comment #2
fumanchu182 commentedReceived a similar error:
* warning: pg_query() [function.pg-query]: Query failed: ERROR: duplicate key violates unique constraint "panels_pane_pkey" in /home/anthony/domains/anthony.thrillist-dev.com/public_html/thrilldrupal/includes/database.pgsql.inc on line 125.
* user warning: query: INSERT INTO panels_pane (pid, did, panel, type, subtype, configuration, cache, access, position) VALUES (0, 34, '', '', '', 'N;', 'a:0:{}', '', 0) in /home/anthony/domains/anthony.thrillist-dev.com/public_html/thrilldrupal/includes/database.pgsql.inc on line 144.
* warning: pg_query() [function.pg-query]: Query failed: ERROR: duplicate key violates unique constraint "panels_pane_pkey" in /home/anthony/domains/anthony.thrillist-dev.com/public_html/thrilldrupal/includes/database.pgsql.inc on line 125.
* user warning: query: INSERT INTO panels_pane (pid, did, panel, type, subtype, configuration, cache, access, position) VALUES (0, 34, '', '', '', 'N;', 'a:0:{}', '', 0) in /home/anthony/domains/anthony.thrillist-dev.com/public_html/thrilldrupal/includes/database.pgsql.inc on line 144.
From watchdog:
Details
Type php
Date Friday, May 30, 2008 - 12:04
User anthony@thrilli...
Location /thrilldrupal/admin/panels/panel-mini/node_panel_page_right/edit/content
Referrer /thrilldrupal/admin/panels/panel-mini/node_panel_page_right/edit/content
Message pg_query() [function.pg-query]: Query failed: ERROR: duplicate key violates unique constraint "panels_pane_pkey" in /home/anthony/domains/anthony.thrillist-dev.com/public_html/thrilldrupal/includes/database.pgsql.inc on line 125.
Severity error
Comment #3
cangeceiro commentedthis appears to be a problem outside of panels, and with drupal core. after recieving this with panels, i recieved the error anytime a module created an entry in the sequences table. once the row existed in the table and i corrected the integers, everything has been running smoothly since.
Comment #4
sdboyer commented@cangecairo - unfortunately, the same doesn't apply in fumanchu's case, as pgsql doesn't use the sequences table.
Given that, however...I don't know what could be causing db_next_id() to fail for pgsql. I'm extremely swamped right now, so anything that points me in the right direction would be very helpful to getting this sorted.
Comment #5
sdboyer commentedHaven't heard anything more on this, and haven't seen any similar issues reported (and this is a big enough problem that I'd imagine I would if it was something systemic), so I'm marking this fixed. Please re-open if that's not the case.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
jbrauer commentedAdding a note here in case anybody finds this looking for Panels in Drupal 6. Seeing an error similar to this indicates you did not disable the modules and uninstall which is necessary as the D5 schema won't work with the D6 version of the module and since there isn't an upgrade path at the moment it will not attempt to change the schema to work with the D6 version.