2.0 to 2.1 upgrade script. Problem with force_unicode_normal_form

[Bill Ott]

Line 2688:
   DROP FUNCTION IF EXISTS public.force_unicode_normal_form (TEXT,TEXT);

Line 6003:
  UPDATE metabib.facet_entry SET value = evergreen.force_unicode_normal_form(value,'NFC');

Without a CREATE FUNCTION between them...

[Bill Ott (bott)]

Doh! schema. Disregard.

[Bill Ott (bott)]

Should line 41 be:

        NEW.value := evergreen.force_unicode_normal_form(NEW.value,'NFC');

instead of:

       NEW.value := force_unicode_normal_form(NEW.value,'NFC');

Since it's no longer public?

[Mike Rylander (mrylander)]

Because of the new search_path rule, it doesn't have to be qualified. However, that would be more clear. Leaving this bug open to keep it on the radar.

[Jason Stephenson (jstephenson)]

Is this relevant any longer?

[Jason Stephenson (jstephenson)]

Hasn't been fixed by now, probably never will be.