Bug 740124 – Text string search on message list view falsely returns "no data to display"

Bug 740124 - Text string search on message list view falsely returns "no data to display"

Summary:	Text string search on message list view falsely returns "no data to display"

Status:	CLOSED CANTFIX

Aliases:	None

Product:	Zanata
Classification:	Community
Component:	Component-UI (Show other bugs)
Sub Component:
Version:	1.4-RC
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Alex Eng
QA Contact:	Ding-Yi Chen
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2011-09-20 22:11 EDT by Ding-Yi Chen
Modified:	2011-09-21 00:33 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-09-21 00:33:44 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ding-Yi Chen 2011-09-20 22:11:02 EDT

Description of problem:
Even search a text string within messages,
it still returns "There is no data to display"

But search numbers works.

Version-Release number of selected component (if applicable):
Zanata version 1.4-alpha-2-SNAPSHOT (20110920-1458)

How reproducible:
Always

Steps to Reproduce:
1. Visit Fedora Readme and one of version.
2. Visit Document Revision_History
3. "Fedora" is on message 2,3,4; click on search field and type "Fedora"
  
Actual results:
message list shows 
"There is no data to display"

Expected results:
Message 2,3,4 are returned, with "Fedora" highlighted.


Additional info:
 Zanata version 1.3 (20110509-2113) does not have this problem

Comment 1 Alex Eng 2011-09-20 22:41:29 EDT

Bug fixed along with https://bugzilla.redhat.com/show_bug.cgi?id=739427 fixes.

Comment 2 Ding-Yi Chen 2011-09-21 00:33:44 EDT

After some investigation, this problem happened in H2 backend ones but not MySQL ones, thus this might be actually H2 bug.

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