mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

I'll not worry at this stage about the view_visit table as that is only
two columns none of which can be null and the data there is
automatically cleaned out after 1 week so there is no old data that
could cause problems.

I'll also not worry about the artefact_log table also as the data saved
there is not retrieved by the mahara system. It looks to just be a paper
trail so devs/admins can see who altered / deleted artefacts within a
group.

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