Re: pgAdmin questions - Mailing list pgsql-general

From bob gailer
Subject Re: pgAdmin questions
Date
Msg-id 310d9a07-1390-940c-80aa-eb0d0d5411b5@gmail.com
Whole thread Raw
In response to Re: pgAdmin questions  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
On 2/3/2018 4:12 PM, Adrian Klaver wrote:
> On 02/03/2018 01:00 PM, bob gailer wrote:
>> On 2/3/2018 3:30 PM, Adrian Klaver wrote:
>>> On 02/03/2018 12:24 PM, bob gailer wrote:
>>>> I am using pgAdmin to create functions (and other wonderful purposes).
>>>
>>>>
>>>> Once I have created a function I notice I can't change the 
>>>> arguments or return type. Why is this? The help topic does not 
>>>> address this.
>>>
>>> Because pgAdmin is just a client over Postgres and creating 
>>> functions is a Postgres responsibility:
>>>
>>>
>>> https://www.postgresql.org/docs/10/static/sql-createfunction.html
>>>
>>> To replace the current definition of an existing function, use 
>>> CREATE OR REPLACE FUNCTION. It is not possible to change the name or 
>>> argument types of a function this way (if you tried, you would 
>>> actually be creating a new, distinct function). Also, CREATE OR 
>>> REPLACE FUNCTION will not let you change the return type of an 
>>> existing function. To do that, you must drop and recreate the 
>>> function. (When using OUT parameters, that means you cannot change 
>>> the types of any OUT parameters except by dropping the function.)"
>> Thanks. That helps. I was misled by seeing -- DROP FUNCTION 
>> public.test(character varying); at the top of the SQL; now I see it 
>> is a comment.
>>>
>>>
>>> For the below you might get better answers quicker on the pgAdmin list:
>> Thanks.
>> Do you refer to pgsql-admin@lists.postgresql.org?
>
> No pgadmin-support:
>
> https://www.postgresql.org/list/pgadmin-support/
I failed to see that in the list. I did not realize I had to scroll down 
to Projects!


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: pgAdmin questions
Next
From: "Mark Scheffer"
Date:
Subject: Looking for workaround to avoid deadlock when using exclusionconstraint