Ticket #10 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Postgres upgrade should work with orphaned content/metadata rows

Reported by: dom Owned by: dom
Priority: normal Milestone: 0.70
Component: wiki-toolkit Version: svn
Keywords: Cc:

Description

The upgrade from the old database schema to new should delete any orphaned content/metadata rows in a similar way to the MySQL upgrade (possibly printing a warning).

Otherwise upgrading a broken database will result in

DBD::Pg::db do failed: ERROR:  column "node_id" contains null values

Change History

Changed 6 years ago by anonymous

Throw a warning, then after setting the node_ids on everthing with a node, do

DELETE FROM content WHERE node_id IS NULL; DELETE FROM metadata WHERE node_id IS NULL;

Changed 6 years ago by dom

  • status changed from new to assigned

Changed 6 years ago by dom

  • status changed from assigned to closed
  • resolution set to fixed

(In [317]) Delete orphaned content/metadata rows in Pg setup (closes #10)

Note: See TracTickets for help on using tickets.