Technical points: view_access currently doesn't limit anything at the code level, so the primary key would simply be the entire row. Any thoughts on what to do here?
Same with view_visit (though there are only two fields here) Review for the other two at https://reviews.mahara.org/856 ** Changed in: mahara Status: Triaged => In Progress -- 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: 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 _______________________________________________ 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