mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

I believe some of the slowness with the view_access table is due to the
lack of a primary key as the db system has to work out indexing itself
based on a number of rows.

I'll add a patch to add a primary 'id' column to the view_access table

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

** Changed in: mahara
   Importance: Low => Medium

** Changed in: mahara
     Assignee: (unassigned) => Robert Lyon (robertl-9)

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

-- 
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