blocktype_installed_category is now done on master but these ones would
require adding a new "id" column:
- artefact_log
- view_access
- view_visit
because they currently don't have to be unique.
** Changed in: mahara
Milestone: 1.5.0 => None
** Changed in: mahara
Assignee: Hugh Davenport (hugh-catalyst) => (unassigned)
** Changed in: mahara
Status: Fix Committed => Confirmed
** Changed in: mahara
Importance: Medium => Low
--
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:
Confirmed
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
_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
