mahara-contributors team mailing list archive

[Mahara Bot <845948@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/5869
Committed: https://git.mahara.org/mahara/mahara/commit/cd9247b48186eff962c3cd9b577790087c8ba24d
Submitter: Aaron Wells (aaronw@xxxxxxxxxxxxxxx)
Branch:    master

commit cd9247b48186eff962c3cd9b577790087c8ba24d
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Date:   Mon Dec 21 13:47:39 2015 +1300

Bug 845948: Add primary key to view_access table for better indexing

Part of the change is to remove duplicate view access rows as there is
no need to have duplicates of the exact same access for a view.

Adding the id to view_access will allow us to have different view
access for a view in multiple collections in the future

behatnotneeded - should be covered by existing tests

Change-Id: I8d3d6f0a011d0ed01a5ff2931e8e16d3000f4f16
Signed-off-by: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Signed-off-by: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>

-- 
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:
  In Progress

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