Missing flush order on TM flags

Bug #599254 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Committed
High
Jeroen T. Vermeulen

Bug Description

Sometimes we clear the is_current (or is_imported, or soon is_current_ubuntu or is_current_upstream) flag on one TranslationMessage and then set it on another. If the ORM flushes the two changes in the reverse order, the second change will violate a unique constraint.

Related branches

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

OOPS-1639O1257
OOPS-1639EC1406

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

May be a duplicate of bug 434738.

Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Changed in rosetta:
status: In Progress → Fix Committed
tags: added: qa-ok
removed: qa-needstesting
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.