Public bug reported: We do this for insert_record() and for ensure_record_exists() but not for update_record()
Normally we pass in the primary key when updating a record so it's already known but some times we update a record via a non primary key column and it would be nice to know the primary key of the row updated. ** Affects: mahara Importance: Medium Status: In Progress -- 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/1711958 Title: Allow the lib/dml update_record() function to return the id of the record updated Status in Mahara: In Progress Bug description: We do this for insert_record() and for ensure_record_exists() but not for update_record() Normally we pass in the primary key when updating a record so it's already known but some times we update a record via a non primary key column and it would be nice to know the primary key of the row updated. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1711958/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp