notification.internal trigger upgrade and MySQL
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Medium
|
Richard Mansfield |
Bug Description
If mahara user in mysql has been created using mahara wiki guide (grant all on (databasename).* to 'username'
Could not execute command: CREATE TRIGGER "update_
Call stack (most recent first):
execute_sql(" CREATE TRIGGER {update_
db_create_
xmldb_notificat
upgrade_
I think upgrade process should be more intuitive and in case of error, it should provide information on permission-related problem along with possible solution (e.g. Your database user might not have been granted TRIGGER permission, please run GRANT TRIGGER on ... ).
Changed in mahara: | |
milestone: | none → 1.5.0 |
importance: | Undecided → Low |
Changed in mahara: | |
status: | New → Triaged |
importance: | Low → Medium |
assignee: | nobody → Richard Mansfield (richard-mansfield) |
Changed in mahara: | |
status: | Triaged → In Progress |
summary: |
- notification.internal trugger upgrade and MySQL + notification.internal trigger upgrade and MySQL |
Changed in mahara: | |
milestone: | 1.5.0 → none |
status: | In Progress → Fix Released |
As Andrew Nicols pointed out, this could be an issue for postgresql too.