mahara-contributors team mailing list archive

[Mahara Bot <845948@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/902
Committed: http://gitorious.org/mahara/mahara/commit/68def4d6b84f0edb9d5044a430d79617e629524d
Submitter: Richard Mansfield (richardm@xxxxxxxxxx)
Branch:    master

commit 68def4d6b84f0edb9d5044a430d79617e629524d
Author: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>
Date:   Wed Nov 30 17:33:40 2011 +1300

    Remove upgrade to add primary key on artefact_log (bug #845948)
    
    The values of artefact,usr columns of the table are not necessarily
    unique.  Perhaps a better option would be to create an id column.
    This primary key was added in a3f6fbfed906be03624dec54e43baed287810cc0.
    
    Change-Id: Ib151a14f0943d799d45a7697abc00f117883cd95
    Signed-off-by: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/845948

Title:
  missing primary keys

Status in Mahara ePortfolio:
  Fix Committed

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