pgAdmin III - bug with reverse engineered SQL with function indexes - Mailing list pgadmin-support

From Donald Fraser
Subject pgAdmin III - bug with reverse engineered SQL with function indexes
Date
Msg-id 002301c35757$91a1fef0$1664a8c0@DEMOLITION
Whole thread Raw
Responses Re: pgAdmin III - bug with reverse engineered SQL  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgadmin-support
pgAdmin III July 16th Build
PostgreSQL 7.3.3
 
The reverse engineered SQL for indexes that use a function do not work.
For example I create an index with the following command:
CREATE UNIQUE INDEX tbl_security_fullname_key
  ON tbl_security
  USING btree (get_securityname_4idx(s_umbname, s_name, s_classname, id));
pgAdmin III produces:
CREATE UNIQUE INDEX tbl_security_fullname_key
  ON public.tbl_security
  USING btree (public.get_securityname_4idx(s_umbname::citext, s_name::citext, s_classname::citext, id::int4) citext_ops);
The problem exists with the appended data type on the column names as the parameters of the function.
If I try to execute pgAdmin's version I get the following error message:
ERROR:  parser: parse error at or near "::" at character 220.
 
 
Regards
Donald Fraser

pgadmin-support by date:

Previous
From: "Luigi Lumento"
Date:
Subject: Re: Problem with plpython editing
Next
From: Andreas Pflug
Date:
Subject: Re: pgAdmin III - bug with reverse engineered SQL