Thread: Why fields are not editable in pgAdmin?

Why fields are not editable in pgAdmin?

From

Michael Monerau

Date:

24 May 2019, 09:15:51

Hello,

Although I am logged in as an Administrator user in pgAdmin4, and with a super user role inside my database, the edition fields are always disabled, as in:

So I can't make modifications with the interface.

Is there some knob to turn on somewhere to allow that?

Re: Why fields are not editable in pgAdmin?

From

Dave Page

Date:

24 May 2019, 09:24:09

On Fri, May 24, 2019 at 10:16 AM Michael Monerau <michael.monerau@gmail.com> wrote:

Hello,

Although I am logged in as an Administrator user in pgAdmin4, and with a super user role inside my database, the edition fields are always disabled, as in:

So I can't make modifications with the interface.
Is there some knob to turn on somewhere to allow that?

No - they're disabled because PostgreSQL doesn't offer a way to modify those options. You have to drop the constraint and add a new one. See https://www.postgresql.org/docs/current/sql-altertable.html

Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: Why fields are not editable in pgAdmin?

From

Michael Monerau

Date:

24 May 2019, 09:46:47

Ah! Nice, makes sense, thanks a lot.

Suggestion: put up a note on the page accessible from the '?' button of the edit dialog box. It links to: http://localhost/pgadmin4/help/help/foreign_key_dialog.html

But the page is for 'creation', so I was left wondering why the screenshots didn't match with what I see.

Hope it helps,

Best,

Michael

Le ven. 24 mai 2019 à 11:24, Dave Page <dpage@pgadmin.org> a écrit :

Hi

On Fri, May 24, 2019 at 10:16 AM Michael Monerau <michael.monerau@gmail.com> wrote:
Hello,

Although I am logged in as an Administrator user in pgAdmin4, and with a super user role inside my database, the edition fields are always disabled, as in:

So I can't make modifications with the interface.
Is there some knob to turn on somewhere to allow that?
No - they're disabled because PostgreSQL doesn't offer a way to modify those options. You have to drop the constraint and add a new one. See https://www.postgresql.org/docs/current/sql-altertable.html

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company