bug in 7.4.2, with Handling of Double Quotation Marks - Mailing list pgsql-general

From Alexander S
Subject bug in 7.4.2, with Handling of Double Quotation Marks
Date
Msg-id 406A83D8.7050307@in.crimea.ua
Whole thread Raw
List pgsql-general
Bug in 7.4.2.. Concern with handling of Double  Quotation Marks (").
Escape of  double quotation marks can't solve the problem.

----------
CREATE TABLE public.test
(
  my_column varchar NOT NULL,
  CONSTRAINT my_primary PRIMARY KEY (my_column)
) WITHOUT OIDS;
-----------
CREATE TABLE public.ref_test
(
  my_column varchar[]
) WITH OIDS;
-----------
CREATE FUNCTION public."t-f_ref_test"()
RETURNS trigger AS
'BEGIN
FOR i IN 1..30 LOOP
    IF NEW."my_column"[i] not in (select "my_column" from public.test) THEN
        RAISE EXCEPTION \'error: my_column[] --> test.my_column \';
    END IF;
END LOOP;
RETURN NEW;
END;'
  LANGUAGE 'plpgsql' VOLATILE;
----------
CREATE TRIGGER t_ref_test
  BEFORE INSERT OR UPDATE
  ON public.ref_test
  FOR EACH ROW
  EXECUTE PROCEDURE public."t-f_ref_test"();
----------
insert into test values (' here \"some_text\" ');
----------
insert into ref_test values (' {here \"some_text\"} ');

But  here  postgres answers:  error: my_column[] --> test.my_column.
So I think this exception should not appear here and this is bug.
Instead I can only insert:
--
insert into ref_test values (' {here \\"some_text\\"} ');       -- but
this is not exactly that i want to have.
--
Without "" in row of public.test - all works fine, but its important for
me to use "" in my templates (database public.test).

pgsql-general by date:

Previous
From: Brent Wood
Date:
Subject: Re: Wich hardware suits best for large full-text indexed
Next
From: google@grossi.co.uk (Peter Grossi)
Date:
Subject: Business packages using postgresql