Bug #72214 Filter Rows: non matching rows are displayed with NULL rows
Submitted: 2 Apr 2014 20:31 Modified: 21 Aug 2014 20:20
Reporter: Stefan Wallner Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.1.4, 6.1.6 OS:Microsoft Windows (8 x64)
Assigned to: CPU Architecture:Any

[2 Apr 2014 20:31] Stefan Wallner
Description:
After using the "Filter Rows: " the non-matching rows are still displayed but only with NULL values.

How to repeat:
CREATE TABLE `tblsources` (
  `idSources` int(11) NOT NULL AUTO_INCREMENT,
  `strSourcesLink` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`idSources`)
) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8;

INSERT INTO `tblsources` VALUES (1,'http://heise.de.feedsportal.com/c/35207/f/653901/index.rss'),(3,'http://rss.winfuture.de/c...');

filter rows: "heise"

result:
# idSources, strSourcesLink
1, http://heise.de.feedsportal.com/c/35207/f/653901/index.rss
NULL, NULL

Suggested fix:
hide non-matching rows
[13 Jun 2014 10:52] Umesh Shastry
Thank you for the report.
Verified as described.

This is even seen with any "SELECT" queries..

Thanks,
Umesh
[4 Aug 2014 15:54] Sam Abboushi
Between this bug (Bug #72214) and
2) Filter Rows no longer works on partial matches (Bug #73465), and
3) the new autofit bugs for the result grid columns (Bug #72332),

I am uninstalling the new version and reinstalling 6.0.6
[21 Aug 2014 20:20] Philip Olson
Fixed as of the MySQL Workbench 6.2.0 release, and here's the changelog entry:

The results grid "Filter Rows" box failed to filter out partial matches.

Thank you for the bug report.