Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sCvdy-0091q6-PB for pgsql-sql@arkaria.postgresql.org; Fri, 31 May 2024 06:21:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sCvdy-009DQ7-RD for pgsql-sql@arkaria.postgresql.org; Fri, 31 May 2024 06:21:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sCvdy-009DOo-HP for pgsql-sql@lists.postgresql.org; Fri, 31 May 2024 06:21:38 +0000 Received: from mail-lj1-x233.google.com ([2a00:1450:4864:20::233]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sCvdv-002mMU-P3 for pgsql-sql@lists.postgresql.org; Fri, 31 May 2024 06:21:37 +0000 Received: by mail-lj1-x233.google.com with SMTP id 38308e7fff4ca-2e95a1f9c53so20461671fa.0 for ; Thu, 30 May 2024 23:21:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717136492; x=1717741292; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=E0XrHDMx/6vK4ph8Qb17ouHm0fdRNjDftyE2jB76qTM=; b=m09zkuytxQ/c14JWoxaOISzgBEZ/Oc6VzXZUH8OW3h3UlbVZ9VHTZSBSX5XxyjX2ne 2FJV59MeTfcamA/I6nfjqDJDSayx93h8GRt99BHUvza2zfIf3lZ8HNWcFZfz916uwyuq Gcz4q9iArzaFeByL+1w00HOOkzg6Hmj1lfwa71oJ4y17dPgpLH+KRSowxx9XivtixVbB SLyUCeiczcckdjj4/DQZ58wweOBgh47Em0VVuHypZRH2oFhOXlfshdA0QUIVSXALMfVu H8Vnd3emFx9X2RRkz+sgUv8yBjaJwEwWMsYvhVxjcdDVyL0IZy7NgLzDi7dALOOjQvbK WeYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717136492; x=1717741292; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=E0XrHDMx/6vK4ph8Qb17ouHm0fdRNjDftyE2jB76qTM=; b=VlG+J0luts6p0YP0jaiRmxMR5cN+l4KQAEzE2Ae+cSG0C3yvN8Y3zwGiSFu1OuFWLl yq+JVZmIp0T7CBgY37ftsAqITLPlP1MrNL94Tq1fUWzQ9Aw3uhHv4iBtehFr+YeZH7eY yKIDXvqJFdGIyleAA/maRVwY0lMjI0+R3LAX9qyi2TkrkOvJu7WhZaT7npkZr8y6KWWy L3XmxwUdcE2ZYRY2UYp9x9TjGNWVIB1cBn6BgVnSAcqgghzYRmT+c8/muuXkEqufdNSA +wXE6xex05hjkDo23oE2mMMNV72OLeM36TYAXXka1e284jiYThivkWdcDfaFy2lkZew5 aWWw== X-Gm-Message-State: AOJu0Yw3VSLUPDsJ6u5fWcs/6jI+YCEkj9Tc6R6TshLoLStB1vhAKs2J tEPXzXW2igePIqN1FMNwf1CT1iBWdggn9g4dBK7VGEEJjXkMgc8Z+UYQx6g3lUKA0eY3y66GUfw vFyzWv68nmEfyMBva+5oAw5axUQo= X-Google-Smtp-Source: AGHT+IG/pPHLfe+ecbU4zIYfgh/xiQbR6931pjDwHjBuDwTqw7SsmkhflRKmmchEJMEhPd3HmxD5+EdL7d14jldakDs= X-Received: by 2002:a2e:a99b:0:b0:2e9:714d:6d1 with SMTP id 38308e7fff4ca-2ea951b6206mr8063911fa.39.1717136491915; Thu, 30 May 2024 23:21:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Muhammad Ikram Date: Fri, 31 May 2024 11:21:12 +0500 Message-ID: Subject: Re: Pgadmin 4 cannot add or modify line in a view To: Amitabh Kant Cc: pgsql-sql@lists.postgresql.org, Steve Midgley , intmail01 Content-Type: multipart/alternative; boundary="000000000000a1bcb00619b9fed2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a1bcb00619b9fed2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, As mentioned above by Usman, you may add/change data via SQL Tool to view or underlying table. There seems to be an issue with PgAdmin, when we right click on *view under Views *in the tree it shows option view/edit though actually it does not allow to Add/Edit data. Regards, Ikram Bitnine On Fri, May 31, 2024 at 7:06=E2=80=AFAM Amitabh Kant wrote: > On Fri, May 31, 2024 at 3:10=E2=80=AFAM Steve Midgley wrote: > >> >> >> On Thu, May 30, 2024 at 7:25=E2=80=AFAM intmail01 = wrote: >> >>> Hi, >>> I tried to modify and add manuallly a line in a view with pgadmin4 but >>> the interface doesnt allow it because cells are locked and no empty lin= e to >>> add new one. >>> The same issues for Libreoffice Base interface. >>> >>> If I do the operation with command UPDATE then it works well . >>> How to permit pgadmin4 to not lock the interface ? >>> >>> I run postgresql 14.1. >>> >>> This group supports the postgres sql language. I think some people here >> might use pgadmin4 (I don't), but I think you'd be better served by the >> pgadmin support list (and docs >> !). >> >> Steve >> > > I assume you are talking about the table data view in pgadmin, rather tha= n > the views supported by postgres SQL language. If that's the case, you mig= ht > be missing a primary key in your table. > --=20 Muhammad Ikram --000000000000a1bcb00619b9fed2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

As mentioned above by Usman, you ma= y add/change data via SQL Tool to view or underlying table.=C2=A0
There seems to be an issue with PgAdmin, when we right click on view un= der Views in the tree it shows option view/edit though actually it does= not allow to Add/Edit data.


Regard= s,
Ikram
Bitnine


On Fri, May 31, 20= 24 at 7:06=E2=80=AFAM Amitabh Kant <amitabhkant@gmail.com> wrote:
On Fri, May 31,= 2024 at 3:10=E2=80=AFAM Steve Midgley <science@misuse.org> wrote:


On Thu, May 30, 2024 at 7:25=E2=80=AFAM int= mail01 <intmail= 01@gmail.com> wrote:
Hi,
I tried to modify and add m= anuallly a line in a view with pgadmin4 but the interface doesnt allow it b= ecause cells are locked and no empty line to add new one.
The sam= e issues for Libreoffice Base interface.

If I do t= he operation with command UPDATE then it works well .
How to = permit pgadmin4 to not lock the interface ?

=
I run postgresql 14.1.

This group supports the postgres sql=C2=A0language. I think some people he= re might use pgadmin4 (I don't), but I think you'd be better served= by the pgadmin support list (and docs!).=C2=A0

<= /div>
Steve

I assume = you are talking about the table data view in pgadmin, rather than the views= supported by postgres SQL=C2=A0language. If that's the case, you might= be missing a primary key in your table.=C2=A0 =C2=A0


--
Muhammad Ikram

--000000000000a1bcb00619b9fed2--