Autosuggest broken in no-vis-check mode
Bug #1053589 reported by
Mike Rylander
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Fix Released
|
Undecided
|
Unassigned | ||
| 2.2 |
Fix Released
|
High
|
Unassigned | ||
| 2.3 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
When autosuggest is configured to avoid visiblity checking, it sends a special org unit id of -1 to the database as a signal. However, the stored procedure is expecting a NULL instead. This allows either by transforming -1 to NULL within the stored procedure.
| no longer affects: | evergreen/2.1 |
| Changed in evergreen: | |
| milestone: | 2.3.1 → none |
Revision history for this message
| Michael Peters (mrpeters) wrote | #1 |
| Changed in evergreen: | |
| status: | New → Confirmed |
Revision history for this message
| Lebbeous Fogle-Weekley (lebbeous) wrote | #2 |
| Changed in evergreen: | |
| status: | Confirmed → Fix Committed |
| milestone: | none → 2.4.0-alpha |
| Changed in evergreen: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Can confirm this as broken, since I think we're the ones who prompted the patch. Not sure about 2.3, however, so I'm leaving that alone.