mahara-contributors team mailing list archive

[Robert Lyon <2009760@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When deleting a person one of the cleanup things that happens is any
multi-recipient notifications for the person are delete also. But when
using MySQL it could cause an issue (segmentation fault) when deleting
then via the admin/cli/delete_inactive_users.php CLI script.

The cause of this was the SQL for creating one of the queries was wrong.

The query ordering syntax was ' ORDER BY ? ' but we can't pass in the
value that way because ADODB will wrap it in quotations and cause things
to fail.

We need to have the query be like this ' ORDER BY ' . $sortby  
so that ADODB doesn't try to quote it.

** Affects: mahara
     Importance: High
         Status: In Progress

** Changed in: mahara
   Importance: Undecided => High

** Changed in: mahara
    Milestone: None => 23.04.0

** Changed in: mahara
       Status: New => In Progress

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

Title:
  Issue with deleteing multirecipient notifications in MySQL

Status in Mahara:
  In Progress

Bug description:
  When deleting a person one of the cleanup things that happens is any
  multi-recipient notifications for the person are delete also. But when
  using MySQL it could cause an issue (segmentation fault) when deleting
  then via the admin/cli/delete_inactive_users.php CLI script.

  The cause of this was the SQL for creating one of the queries was
  wrong.

  The query ordering syntax was ' ORDER BY ? ' but we can't pass in the
  value that way because ADODB will wrap it in quotations and cause
  things to fail.

  We need to have the query be like this ' ORDER BY ' . $sortby  
  so that ADODB doesn't try to quote it.

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