mahara-contributors team mailing list archive

[Nigel Cunningham <nigelc@xxxxxxxxxxxxxxx>]

Public bug reported:

In ArtefactType::commit, we shouldn't bother calling delete_records if
we know the artefact that is being committed is new. In testing the
addition 2000 users from a CSV file, this patch shaved 4 seconds off the
completion time.

** Affects: mahara
     Importance: Undecided
     Assignee: Nigel Cunningham (nigelc-g)
         Status: In Progress

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

** Changed in: mahara
     Assignee: (unassigned) => Nigel Cunningham (nigelc-g)

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

Title:
  ArtfactType::commit - don't delete records when none exist

Status in Mahara ePortfolio:
  In Progress

Bug description:
  In ArtefactType::commit, we shouldn't bother calling delete_records if
  we know the artefact that is being committed is new. In testing the
  addition 2000 users from a CSV file, this patch shaved 4 seconds off
  the completion time.

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