z3950_attr_name_is_valid should be STABLE, not IMMUTABLE

Bug #1413660 reported by Bill Erickson on 2015-01-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned
2.6
Undecided
Unassigned
2.7
Undecided
Unassigned

Bug Description

Evergreen all, circa 2.7.

The SQL function evergreen.z3950_attr_name_is_valid() may return different values with the same input and should not be marked as IMMUTABLE. Patch en route.

Bill Erickson (berick) wrote :
Changed in evergreen:
milestone: none → 2.8-beta
tags: added: pullrequest
Mike Rylander (mrylander) wrote :

While true, and a good change, were you seeing an effect from IMMUTABLE? Perhaps changes not being picked up within a db session?

Bill Erickson (berick) wrote :

No, I didn't see any effect. This was purely academic.

Bill Erickson (berick) wrote :

... and the result of some thoughtless cargo-culting on my part in the original code.

Ben Shum (bshum) wrote :

Picked to master, rel_2_7, and rel_2_6.

Changed in evergreen:
status: New → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers