ItEr61S07PerformanceOrderEdition

TWiki> LibrePlan Web>ItEr61S07PerformanceOrderEdition (01 Oct 2010, JoseMariaCasanova)EditAttach

ItEr61S07PerformanceOrderEdition

Story summary	Performance improvements in order edition
Iteration	ItEr61week38To40
FEA	ItEr61S07PerformanceOrderEdition
Story Lead
Next Story
Passed acceptance test	No

Acceptance Criteria

Additional Specification Comments

Implementation Notes

There was a considerable bottleneck related to validation when an Order is saved. For each order, there is a constraint checking that validates none each HoursGroup? .code is unique. This is done for each OrderElement? within an Order, when it should be a big improvement to do all this checking in one pass. To do that, it's necessary to move this validation to OrderModel. This approach has being already done for OrderElement.code.

This change implies that is necessary to add this checking to OrderElementService too.

The entity HoursGroup extends now from IntegrationEntity.

Delay Causes

Final or Pending Considerations

Entregables de código

%RPSHOWGITCOMMITS%

Tasks in this story

Tasks	Est	Spent	To do	Risk	Reviewer	Developer	Task Name	Start Date	Est End Date	End Date
Task	10	9.25	0	Low	JavierMoran	DiegoPino	Change validation of unique order code and hours group from entity to XXXModel

---

Total Hours in this Story

User	Spent in XpTracker	Spent in phpReport	Ok?
DiegoPino	9.25	0
Total	9.25	0

Copyright (c) by the contributing authors. All material on this collaboration platform is the property of the contributing authors.