mahara-contributors team mailing list archive

[Aaron Wells <845948@xxxxxxxxxxxxxxxxxx>]

Current Mahara policy is to add a primary key ID column to every new
table, but in most cases to not bother adding them to existing tables.

** Changed in: mahara
    Milestone: 1.9.0 => None

** Changed in: mahara
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/845948

Title:
  missing primary keys

Status in Mahara ePortfolio:
  Won't Fix

Bug description:
  It seems during the installation of Mahara several tables are created
  without primary keys. This caused a headache for us when restoring
  tables from a pg_dump script, duplicate records were created.
  Specifically the table 'blocktype_installed_category', caused
  duplicate block types in the UI (confusing some users). A further
  check revealed the following tables also missing primary keys:

  artefact_log
  view_access
  view_visit
  blocktype_installed_category

  Version: 1.4.0
  Database: Postgres
  OS: Linux/RHEL

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/845948/+subscriptions