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 1sCnda-008CD5-Ol for pgadmin-hackers@arkaria.postgresql.org; Thu, 30 May 2024 21:48:44 +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 1sCnda-006Mhm-LW for pgadmin-hackers@arkaria.postgresql.org; Thu, 30 May 2024 21:48:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sCl7f-005KOE-Hk; Thu, 30 May 2024 19:07:35 +0000 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sCl7Y-001YSB-9f; Thu, 30 May 2024 19:07:34 +0000 Received: by mail-oi1-x233.google.com with SMTP id 5614622812f47-3d1bb1c3b74so739219b6e.2; Thu, 30 May 2024 12:07:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717096047; x=1717700847; 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=mLR5PDt6f2HbGe7Jw+YHnEqSdUnM7P8Bu3K6u4+/H4g=; b=Lq0M46Kf0WFS7eZ9ppfWPXEBW0dWWlYjfye3UgR8D2H2R6UKhgTl3CdynC1e/Y2Boh rGEAhF0XW8Kwiex6Vv7ENSywLvCN/9qQ7kMg3GKeEsVL+P+mo0qCyn4xHZLtEQlgRyPu EqhBKsnsvqo3A46ictGceyPs+LibJ09z5qPwvIfknt+Zz6zgRJtmWDpbH/zGTmpsQgoq Zrb8hgxhJBU7konQ0oaJKPheSicPNh9FVte+Rs3+caU1H9GYMvIc2QNUese+ZPtsbB2n F3p9rrf7CLf3mib2JXiL/uCZO3yX9fGG78dL/yNHnuVyX7ttDXqb2ncaUUEdmVhdwGmu 4yGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717096047; x=1717700847; 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=mLR5PDt6f2HbGe7Jw+YHnEqSdUnM7P8Bu3K6u4+/H4g=; b=DIkGyRqQH9u2vmhEpjh8Z1vFI/r1yPKoROhpDu3iVqgfBKRkIemHmJeF7x7bXYPtPm YdIsMhOIL9YXDa+FbylaVn5NMgoNwGGin4JIr87Zvmi0D9auxFFOMUTAicQAVVqxhiUt zpZY+Od3zCvmlwvKAGT7bWN7PCIpVlr+ynh2MQy+O55bnxm+cRu5XmBgBsWSnp8hmQkP j910Gfxo2xQlNKirkMa6+X3K8+8ae+PEMHD/W/yRyrUxveeVyNtSOJRT6CIaRdbg8O2i czZKUWoj2ThYeqgp/pOkmQb8BqLq/xfQd6XIp7wiREwAm5ECgBPmCbHilCD7plFOdcRB cJfA== X-Forwarded-Encrypted: i=1; AJvYcCWnZ3d57xN58akJX/2BHj/QWw255o4OfemBinAecaf4moAJkTmQbsBOxoX0eNYJW5zQFftzTFzLLpgHHGcOYxFQ6awd6oTjkXHyU0pBIH0= X-Gm-Message-State: AOJu0YyKoMbdm5ZIbBw/bhOdgxIaAuO+rJpxiDH34Kj/uHy2uMzb15Ox nqmBWmirApmfXygran5L/CxQ0g2H2715TDSY9JMoyi6M6OOBENdkoU3xiisK241T39HM0X7Bhef mac/EzPMioeChfkKY7uYb4nawsNs= X-Google-Smtp-Source: AGHT+IGJm9sYdyHkqlT57IzLQkubzb1UnZ1f6+dVxyednowFQ9FhvhEse5CrPGWsjM59827E46UB7w2uhl7sk69EKKg= X-Received: by 2002:a05:6870:d88f:b0:250:8248:7ea7 with SMTP id 586e51a60fabf-2508248a6a1mr995385fac.27.1717096046588; Thu, 30 May 2024 12:07:26 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Usman Khan Date: Fri, 31 May 2024 00:07:15 +0500 Message-ID: Subject: Re: Pgadmin 4 cannot add or modify line in a view To: intmail01 Cc: pgadmin-hackers@lists.postgresql.org, pgsql-sql@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000e700270619b093ba" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e700270619b093ba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Kindly go through this document for more details about view being non editable https://www.pgadmin.org/docs/pgadmin4/development/editgrid.html On Thu, May 30, 2024 at 10:59=E2=80=AFPM intmail01 wr= ote: > I read the PostgreSQL manual and view can be modified if some rules are > respected. My query is very simple and follow rules : SELECT * FROM > thePartionedTable > When I run code with INSERT and UPDATE clause then it work fine. > In fact the view comes from a partitioned table. After an INSERT or UPDAT= E > I checked both source tables and they are well updated. > > The reason why Pgadmin locks the array may come from the fact there is n= o > defined primary key. My partitioned table have primary key. > I do not have any idea how to re-define again a primary key for a view. > > Thanks > > On Thu, May 30, 2024 at 5:52=E2=80=AFPM Usman Khan wro= te: > >> >> Can you please elaborate your requirement a bit more? >> The result grid is usually non editable for views. You can edit table >> data to reflect values in view. >> >> Note : adding pgadmin-hackers for more guidance. >> >> >> On Thu, May 30, 2024 at 7:25=E2=80=AFPM 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. >>> >>> Thanks >>> >> --000000000000e700270619b093ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
Kindly go through this document for mor= e details about view being non editable

On Thu, May 30, 2024= at 10:59=E2=80=AFPM intmail01 <i= ntmail01@gmail.com> wrote:
I read the PostgreSQL manual and vi= ew can be modified if some rules are respected. My query is very simple and= follow rules : SELECT * FROM thePartionedTable
When I run co= de with INSERT and UPDATE clause then it work fine.
In fact the v= iew comes from a partitioned table. After an INSERT or UPDATE I checked bot= h source tables and they are well updated.

The reason why Pgadmin locks the array may=C2=A0 come from the fact= there is no defined primary key. My partitioned table have primary key.
I do not have any idea how to re-define again a primary key for a v= iew.

Thanks

On Thu, May 30, 2024 at 5:52= =E2=80=AFPM Usman Khan <umk555@gmail.com> wrote:

Can you please elaborate your requirement a bit more?
The result grid is usually non editable for views. You can edit = table data to reflect values in view.

Note : adding pgadmin-hackers for more guidance.


On= Thu, May 30, 2024 at 7:25=E2=80=AFPM intmail01 <intmail01@gmail.com> wrote:
= Hi,
I tried to modify and add manuallly a line in a view with pga= dmin4 but the interface doesnt allow it because cells are locked and no emp= ty line to add new one.
The same issues for Libreoffice Base inte= rface.

If I do the operation with command UPDATE t= hen it works well .
How to permit pgadmin4 to not lock the in= terface ?

I run postgresql 14.1.

Thanks
--000000000000e700270619b093ba--