mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #44059
[Bug 1711958] A change has been merged
Reviewed: https://reviews.mahara.org/7938
Committed: https://git.mahara.org/mahara/mahara/commit/d73a4a9e6a35a369cbda31ab2e6ffedd2d2b2cd6
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch: master
commit d73a4a9e6a35a369cbda31ab2e6ffedd2d2b2cd6
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Date: Mon Aug 21 09:34:46 2017 +1200
Bug 1711958: Allow update_record to return id of record updated
By supplying $primarykey and $returnpk parameters to the update_record
function
behatnotneeded
Change-Id: Ib2078384cf2d48e4cea1b08f804ea01dc8e9b1d4
Signed-off-by: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
--
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:
Fix Committed
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
References