mahara-contributors team mailing list archive

[Mahara Bot <1264429@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/2870
Committed: http://gitorious.org/mahara/mahara/commit/5be3b920903cd00da4f837064928364a70430124
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    master

commit 5be3b920903cd00da4f837064928364a70430124
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Fri Dec 27 16:39:19 2013 +1300

Introducing the institution_config table

Bug 1264429: This patch creates the table, refactors the get_institution_config() method,
the Institution class, and the institution editing page, to use the new table.

Henceforth columns should only be added to the main "institution" table if they represent
a required setting (like name and displayname), or they need to be accessed frequently by
direct SQL queries.

Change-Id: I4564240d2c55ec2b6ec90868290a61cf4321460a

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

Title:
  Set up an institution_config table for configuring institutions

Status in Mahara ePortfolio:
  In Progress

Bug description:
  We've been adding a lot of new institution configuration parameters
  lately, so it makes sense to add an "institution_config" table to
  handle these so that we don't have to add a new column to the
  "institution" table each time we want to add some new bit of
  configuration.

  This can be integrated into the Institution class and the
  get_config_institution() methods so that the programmer accessing the
  field doesn't need to know whether it's in the "institution" table or
  the "institution_config" table.

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