Bug 864297 - Text Flow Target History contains an entry for the initial empty string
Summary: Text Flow Target History contains an entry for the initial empty string
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Logic
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2.0
Assignee: Carlos Munoz
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-09 04:28 UTC by Carlos Munoz
Modified: 2013-02-26 03:46 UTC (History)
2 users (show)

Fixed In Version: 2.0.3-SNAPSHOT (20121119-0019)
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-26 03:46:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Carlos Munoz 2012-10-09 04:28:25 UTC
Description of problem:
Text Flow target history contains an empty entry after an initial save.


Version-Release number of selected component (if applicable):
1.8-SNAPSHOT

How reproducible:
Always (found on a po project with plurals)


Steps to Reproduce:
1. Try to edit a text flow on any project.
2. Visit the History screen.
  
Actual results:
There is an entry in the history screen for an initial "empty" state. This entry cannot be copied into the editor.

Expected results:
There should only be a single history entry after the initial save. One for the current latest state.

Comment 1 Carlos Munoz 2012-11-09 00:40:21 UTC
This was caused by an incorrect use of Hibernate entity listeners. The new implementation uses DB triggers again. Please retest.

Comment 2 Sean Flanigan 2012-11-09 02:30:16 UTC
This change is in the current release (2.0.2), isn't it?  So if we verify it, it can move straight to 'closed'.

Comment 3 Carlos Munoz 2012-11-09 02:39:31 UTC
That's right, this is already in 2.0.2.

Comment 4 Ding-Yi Chen 2012-11-19 04:42:13 UTC
VERIFIED 
with Zanata version 2.1-SNAPSHOT (20121119-1207)
and Zanata version 2.0.3-SNAPSHOT (20121119-0019)


Note You need to log in before you can comment on or make changes to this bug.