Given the following trivial trigger example:
-- create language plpgsql;
create table foo (a integer, b text, c timestamp);
create function foo_insert() returns trigger as $$
begin
raise notice '%', new;
return null;
end;
$$ language plpgsql;
create trigger foo_ins before insert on foo
for each row execute procedure foo_insert();
insert into foo values (1, 'two', current_timestamp);
I am surprised to see
NOTICE: (1,two,"Sat 09 Feb 16:47:44.514503 2008")
INSERT 0 0
I would have expected
NOTICE: (1,'two','Sat 09 Feb 16:47:44.514503 2008')
INSERT 0 0
i.e., a row whose columns look as though they went through quote_literal
rather than through quote_ident.
This is with yesterday's 8.3.0 (Feb 8 17:24 GMT)
Thoughts?
Cheers,
Patrick
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly