mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

Hi Rebecca,

With the 3 'Anomalies' we could fix up by adding an id column to the
tables and then having that id be used in it's place else where, eg for
view_type add an id column and then in view table in type column have
the id rather than the word.

It would mean a bunch of changes and in the PHP code / SQL query
structure to get things working right.

For the denormalized 'usr_friend' table it does kinda make sense to have
usr1 and usr2 as they are users equal in weighting. Though we could
change it to 'friend' and 'befriended' perhaps to make things clearer

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

Title:
  Database anomalies and orphan tables

Status in Mahara:
  New

Bug description:
  While investigating how to map out Mahara and see what connects to
  what a discovered a db schema-mapping tool. (Details in the bug
  report: https://bugs.launchpad.net/mahara/+bug/1855630)

  That highlighted some issues with our db schema:

  'Anomalies'
  We have 3 tables that contain a single column:
  artefact_comment_deletedby
  event_type
  view_type

  We have 1 table with incrementing column names, potentially indicating denormalization
  usr_friend

  We have a number of orphan tables listed in the comment below.

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