Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Orderable Version Increment (PUT)

Description

As a developer I want the Orderable version indicator to update when I update the Orderable so that each change to an Orderable has a unique version Id.

AC:

  • PUT /api/Orderable causes the versionId += 1

  • Version incrementing should be enforced at the repository level.

  • If the request body contains a versionId, it should be stripped and ignored.

Notes

  • version should be incremented if program orderable was changed

Confluence content

mentioned on

Activity

Show:
Paulina Buzderewicz
June 18, 2019 at 12:36 PM

As the result of this discussion: https://forum.openlmis.org/t/orderable-version-incrementing/5162/4, we decided to leave the version increment on the service level and to add the isolation level to ensure more safety when updating an orderable. This is why this ticket https://openlmis.atlassian.net/browse/OLMIS-6390 was created. In such case I’m moving this one to Dead.

Paulina Buzderewicz
June 5, 2019 at 2:08 PM
(edited)

I have a question related to this ticket. As the versionId field is inside the embeddable class, the solution for incrementing this version is not as simple as just using @Version annotation to this field. The only idea which we have for now is to create a trigger procedure. Do you think it would be the appropriate solution here? Or maybe you have another idea?

Won't Fix
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Original estimate

Time tracking

3d 5h 30m logged2h 30m remaining

Sprint

None

Priority

Parent

Time Assistant

Created March 6, 2019 at 1:30 AM
Updated February 8, 2023 at 1:29 PM
Resolved June 18, 2019 at 12:37 PM