mahara-contributors team mailing list archive

[Robert Lyon <1999594@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

We removed a bunch of db triggers in Mahara and made them pseudo
triggers (handled by PHP rather than the database) but we didn't remove
the trigger check / db_*_trigger() functions.

We should make the next Mahara be a hard upgrade point so that we can
then  safely remove the checks/functions in a patch after this point as
sites will not be able to jump past this point to upgrade to a later
version and find the trigger stuff missing. They will have to step to
this point before upgrading further.

** Affects: mahara
     Importance: Undecided
         Status: New

** Description changed:

  We removed a bunch of db triggers in Mahara and made them pseudo
  triggers (handled by PHP rather than the database) but we didn't remove
  the trigger check / db_*_trigger() functions.
  
  We should make the next Mahara be a hard upgrade point so that we can
- safely remove the checks/functions as sites will not be able to jump
- past this point to upgrade to a later version.
+ then  safely remove the checks/functions in a patch after this point as
+ sites will not be able to jump past this point to upgrade to a later
+ version and find the trigger stuff missing. They will have to step to
+ this point before upgrading further.

** Summary changed:

- Remove all code relating to db triggers
+ Create a hard point upgrade so we can remove code relating to db triggers after that point

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/1999594

Title:
  Create a hard point upgrade so we can remove code relating to db
  triggers after that point

Status in Mahara:
  New

Bug description:
  We removed a bunch of db triggers in Mahara and made them pseudo
  triggers (handled by PHP rather than the database) but we didn't
  remove the trigger check / db_*_trigger() functions.

  We should make the next Mahara be a hard upgrade point so that we can
  then  safely remove the checks/functions in a patch after this point
  as sites will not be able to jump past this point to upgrade to a
  later version and find the trigger stuff missing. They will have to
  step to this point before upgrading further.

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