Re: locale operation to be invoked, but no collation was derived (in trigger)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Huehner <stefan(at)huehner(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: locale operation to be invoked, but no collation was derived (in trigger)
Date: 2011-03-25 22:46:50
Message-ID: 17021.1301093210@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stefan Huehner <stefan(at)huehner(dot)org> writes:
> first i am not sure how the state of the collation work in current git is supposed to be with all the discussion going on here... but wanted to get out that bug report:

> create table ad_tab (ad_tab_id varchar(32), name varchar(32));

> create function test_trg() RETURNS TRIGGER LANGUAGE plpgsql AS $function$ DECLARE
> BEGIN
> --Check tab name starts with a upper case letter
> IF (not (substr(new.Name,1,1) between 'A' and 'Z')) THEN
> RAISE EXCEPTION '%', '@TabName1stCharUpper@' ; --OBTG:-20000--
> END IF;
> END
> ; $function$
> ;

> create trigger test_trg after update on test for each row execute procedure test_trg();

> insert into test values ('1', 'test');
> update test set name = 'test2' where test_id = '1';

> ERROR: locale operation to be invoked, but no collation was derived
> CONTEXT: PL/pgSQL function "test_trg" line 4 at IF

Fixed, thanks for the test case. (I have a feeling I'd better grep the
whole backend for other places that are likewise neglecting to set the
collation fields in manually-created expression nodes ...)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-25 22:59:09 Re: WIP: Allow SQL-language functions to reference parameters by parameter name
Previous Message Simon Riggs 2011-03-25 22:18:40 9.1 Beta