pgAdmin III - bug with reverse engineered SQL with function indexes

From: "Donald Fraser" <demolish(at)cwgsy(dot)net>
To: "[pgADMIN]" <pgadmin-support(at)postgresql(dot)org>
Subject: pgAdmin III - bug with reverse engineered SQL with function indexes
Date: 2003-07-31 11:33:25
Message-ID: 002301c35757$91a1fef0$1664a8c0@DEMOLITION
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Andreas Pflug 2003-07-31 12:36:19 Re: pgAdmin III - bug with reverse engineered SQL
Previous Message Hiroshi Saito 2003-07-31 08:30:43 Fw: Migration error: Provider not found