Re: pgAdmin III - SECURE DEFINER instead of SECURITY DEFINER

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Donald Fraser" <demolish(at)cwgsy(dot)net>, "[pgADMIN]" <pgadmin-support(at)postgresql(dot)org>
Subject: Re: pgAdmin III - SECURE DEFINER instead of SECURITY DEFINER
Date: 2003-07-17 11:44:32
Message-ID: 03AF4E498C591348A42FC93DEA9661B844B31D@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Thanks, fixed in CVS.

Regards, Dave.

-----Original Message-----
From: Donald Fraser [mailto:demolish(at)cwgsy(dot)net]
Sent: 17 July 2003 11:41
To: [pgADMIN]
Subject: [pgadmin-support] pgAdmin III - SECURE DEFINER instead
of SECURITY DEFINER


pgAdmin III July 16th build.

When I try to edit a function via the properties dialog and I
have the "Secure definer" check box item selected on the first tab-page
I get errors like:

ERROR: parser: parse error at or near "SECURE" at character 364
Looking at the log file it is appending the text "SECURE
DEFINER" instead of "SECURITY DEFINER".

Regards
Donald Fraser.

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2003-07-17 14:45:17 pgAdmin II 1.6.0 Released
Previous Message Donald Fraser 2003-07-17 10:40:49 pgAdmin III - SECURE DEFINER instead of SECURITY DEFINER