Evergreen

Browse normalization timing is incorrect

Bug #1214560 reported by Mike Rylander
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
Evergreen 2.4.2
2.3
Fix Released
Medium
Unassigned
Evergreen 2.3.11
2.4
Fix Released
Medium
Unassigned
Evergreen 2.4.2

Bug Description

When indexing browse entries, we need to normalize the value we want to use
before we go looking for it in the table, for uniqueness. We do in master,
we need to in 2.4 (and before) as well.

Here's the 2.4 branch to do that: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/browse_entry_normalization_timing

Tags: pullrequest
Revision history for this message
Mike Rylander (mrylander) wrote :

And here's a 2.3 version: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/browse_entry_normalization_timing_23

Revision history for this message
Ben Shum (bshum) wrote :

Added to 2.3 and 2.4 branches. Put a placeholder for 0821 in master as well.

Changed in evergreen:
status: New → Fix Committed
importance: Undecided → Medium
Ben Shum (bshum)
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.