Back to bug 1302443

Who When What Removed Added
Tim Wade 2016-01-28 17:18:34 UTC Status NEW ASSIGNED
Assignee gtanzill twade
Chris Pelland 2016-02-11 16:47:35 UTC Keywords ZStream
Chris Pelland 2016-02-11 17:00:16 UTC Target Release 5.6.0 5.5.3
Tim Wade 2016-02-11 18:20:09 UTC Status ASSIGNED ON_DEV
Tim Wade 2016-02-19 20:43:14 UTC Status ON_DEV POST
John Prause 2016-02-19 21:05:37 UTC Status POST MODIFIED
Marianne Feifer 2016-02-24 19:37:42 UTC CC mfeifer
Doc Text Cause: Unable to filter the resources using name parameter with REST API.


Consequence: Name" parameter does not work with category Collection for querying (

Fix: Currently API results can't be filtered by virtual attributes. This is because all filter attributes are contructed into a SQL query regardless of whether they represent column names. Filtering by virtual attributes would result in a database error.

This change will check for non-column attributes before making the query, and attempt to filter by them in ruby after the results are returned.

Result:
errata-xmlrpc 2016-03-22 10:57:51 UTC Status MODIFIED ON_QA
John Prause 2016-03-22 12:33:47 UTC Fixed In Version 5.5.3.2
Dayle Parker 2016-03-23 05:54:07 UTC Doc Text Cause: Unable to filter the resources using name parameter with REST API.


Consequence: Name" parameter does not work with category Collection for querying (

Fix: Currently API results can't be filtered by virtual attributes. This is because all filter attributes are contructed into a SQL query regardless of whether they represent column names. Filtering by virtual attributes would result in a database error.

This change will check for non-column attributes before making the query, and attempt to filter by them in ruby after the results are returned.

Result:
Previously, the REST API could not filter resources using the name parameter. This was because all filter attributes were contructed into a SQL query regardless of whether they represent column names, and thus filtering by virtual attributes would result in a database error. The code now checks for non-column attributes before making the query, and filters by them in Ruby after the results are returned.
Dayle Parker 2016-03-23 05:55:02 UTC Doc Text Previously, the REST API could not filter resources using the name parameter. This was because all filter attributes were contructed into a SQL query regardless of whether they represent column names, and thus filtering by virtual attributes would result in a database error. The code now checks for non-column attributes before making the query, and filters by them in Ruby after the results are returned. Previously, the REST API could not filter resources using the name parameter. This was because all filter attributes were constructed into a SQL query regardless of whether they represent column names, and thus filtering by virtual attributes would result in a database error. The code now checks for non-column attributes before making the query, and filters by these attributes in Ruby after the results are returned.
Dayle Parker 2016-03-24 01:16:07 UTC Doc Text Previously, the REST API could not filter resources using the name parameter. This was because all filter attributes were constructed into a SQL query regardless of whether they represent column names, and thus filtering by virtual attributes would result in a database error. The code now checks for non-column attributes before making the query, and filters by these attributes in Ruby after the results are returned. Previously, the REST API could not filter resources using the name parameter. This was because all filter attributes were constructed into a SQL query regardless of whether they represented column names, and thus filtering by virtual attributes would result in a database error. The code now checks for non-column attributes before making the query, and filters by these attributes in Ruby after the results are returned.
dajohnso 2016-03-24 21:12:37 UTC QA Contact dajohnso jteehan
Jeff Teehan 2016-04-07 18:53:14 UTC Status ON_QA VERIFIED
errata-xmlrpc 2016-04-13 03:46:23 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-04-13 18:42:02 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-04-13 14:42:02 UTC

Back to bug 1302443