sorting a field that has null values fails
Bug #1741400 reported by
Kushal Agrawal
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Glare |
In Progress
|
High
|
Kushal Agrawal | ||
Bug Description
In case of a field is both "sortable" and "nullable", When a user tries to fetch artifact list sorted based on the nullable field. Glare gives an error response with 500 Error with below Error Message.
<html>
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h1>500 Internal Server Error</h1>
Only '=', '!=', 'is_()', 'isnot()', 'is_distinct_
<br />
<br />
</body>
</html>
| Changed in glare: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| Changed in glare: | |
| assignee: | nobody → Kushal Agrawal (kushal2605) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to glare (master) | #1 |
| Changed in glare: | |
| status: | Confirmed → In Progress |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/