mahara-contributors team mailing list archive

[Nathan Lewis <nathan.lewis@xxxxxxxxxxxxx>]

Public bug reported:

We are going to be adding some complex queries that require that
institutions can be looked up by an integer id. We need an int for
performance reasons and also the ability to store an "object id" which
could contain institution ids, group ids, artefact ids, page ids etc,
all in the same field.

As discussed with Aaron, the name field will continue to be the primary
key and used in most places in Mahara. This patch doesn't utilise the
field anywhere, it is preparation for future patches.

Version: master

** Affects: mahara
     Importance: Undecided
         Status: New

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

Title:
  Add id field to institution table

Status in Mahara ePortfolio:
  New

Bug description:
  We are going to be adding some complex queries that require that
  institutions can be looked up by an integer id. We need an int for
  performance reasons and also the ability to store an "object id" which
  could contain institution ids, group ids, artefact ids, page ids etc,
  all in the same field.

  As discussed with Aaron, the name field will continue to be the
  primary key and used in most places in Mahara. This patch doesn't
  utilise the field anywhere, it is preparation for future patches.

  Version: master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1300997/+subscriptions