Closed (fixed)
Project:
Panels
Version:
5.x-2.0-beta3
Component:
Views panes
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 May 2008 at 17:15 UTC
Updated:
31 Jul 2008 at 04:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
sdboyer commentedThanks for this, I still haven't had the time to set up my local pgsql db for testing. I'll review & likely commit these when I get a minute.
Comment #2
stormsweeper commentedOops, missed the sequence. I added another check that changes the definition of the primary key column to 'serial PRIMARY KEY' for pgsql. Sequences created thusly are "attached" to the table, so no need for further uninstall sql.
Comment #3
stormsweeper commentedAttaching the file again this time.
Comment #4
sunoffset bug has been fixed in the meantime.
And, a primary key is not the same as auto_increment, which is what 'serial' type columns are intended for.
Comment #5
stormsweeper commentedThe {panels_views}.pvid column is a sequence-driven column, and if you don't have a sequence declared for the column you will get errors when actually using the module to create a new views pane. The mySql-specific sequences table will handle undeclared sequences but that is of no use in Postgres. The serial type is used for all such primary key columns in Drupal core to avoid exactly what I am avoiding here - having to have explicit calls to create and destroy the sequences.
http://www.postgresql.org/docs/7.4/interactive/datatype.html#DATATYPE-SE...
Comment #6
stormsweeper commentedNew patch attached, made against the DRUPAL-5--2 branch.
Comment #7
sdboyer commentedComment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.