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 1sCkOk-007oeV-BK for pgadmin-hackers@arkaria.postgresql.org; Thu, 30 May 2024 18:21:11 +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 1sCkOk-00545f-2I for pgadmin-hackers@arkaria.postgresql.org; Thu, 30 May 2024 18:21:10 +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 1sCk4G-004zKK-1p; Thu, 30 May 2024 18:00:00 +0000 Received: from mail-oa1-x32.google.com ([2001:4860:4864:20::32]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sCk4D-001Y0d-BN; Thu, 30 May 2024 17:59:59 +0000 Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-250671a1bc7so128192fac.3; Thu, 30 May 2024 10:59:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717091996; x=1717696796; 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=mJdwJs73sIcATrSqY4zRzhnCkudqr1r2hwuN4/VUnl8=; b=lDAgeI9qpKHgG3vLCx3mvD12raBNJ+UZ9LKO3miqGglVRLfcjaQqcsWmIbtMYDtv7m NIxUzyqLc0EbmQ2WpEoK/P2CNmH6iqHCs7/3e5svCsYCOZo/cKf5pIOXCAuuYQO9+vRX AHE4TkbkwHoN5odk00r/ZNG+r4bOB7UM7E/KxTOTr5ikH+HZTYxWA4SP1F2j0qN+VL2M jKVOvDWNS4P4UEqxncSjSpB2pcnlJ+cuSFtO40rBFI9BEVwQAaXCvW5pGoPc02TomO+K 0b3SJEMW39Fet6ms+NcyuLoM0Oc4948YyVG6vf4+azXb6bg2FS/cpXIYiy6tDAsjdM3C /IUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717091996; x=1717696796; 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=mJdwJs73sIcATrSqY4zRzhnCkudqr1r2hwuN4/VUnl8=; b=V3kvQ3zMlepDcVWJxwjEl+Is972DLJM5TYbylr1y+0rKR1t20BZrE9t6bmPvrrHfFA ppQ6RNPUyQ1qF0YxAoIgB4zpaatOxfkpkUWGdmKOQNvw9S4JLUNKoJPLSKiUolCcBwqY 09RQM9AZ9bothlZqJIvjw9ZVZawdYar53ILrDKcuK2Na0CT4amg5e3htH9025EhDdwnv cTX7wUl/Dz4f77Ln1KAw3aAwYOOoerCX6vMeDxXv73XfxCwE8XQWXOZYkeBwTVbRswki IQIrx88FcbqJuqq9TXzyhsMCi4+sKatrjUuPZt+tGgtDQ2Oo9Jfl5+j6WiQtQ2+Te78L xDyw== X-Forwarded-Encrypted: i=1; AJvYcCUHTY2VSVtsVa+Q6QlfL7TO4+U/mKjUaMad1mqBQxNW/XCBBMAltX0kGFcD9m4EjeyZUHmdUl6GMHT297Ah4w6uU/coVJ79qxv/Mxbd8YY= X-Gm-Message-State: AOJu0YzFsD0HiHqQaIWYie60YnjGTqaGklRgLSaXvAIZRmUQm8jjfG4J tvAP1Ep/SOhxHI/IiZFPkFZDn/SlyppBGEMqEYXV6PApZQSnOI0cc2O7WrYPV3hPMgZZiDBWm8e i9f3I6pZrdXPK5AA5Ch2la1cBjn84uZUfzw0= X-Google-Smtp-Source: AGHT+IFRXId/cDsvGIvdyOxkksHOP4ycJG3Tm8i2KqpyB3GNmeZEzE0d31iYzWybqcsyLwKiWkC7rscEk4z2UybUVJo= X-Received: by 2002:a05:6870:6392:b0:250:5c1:5d3f with SMTP id 586e51a60fabf-25060dc40e7mr3215562fac.56.1717091995527; Thu, 30 May 2024 10:59:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: intmail01 Date: Thu, 30 May 2024 21:01:16 +0300 Message-ID: Subject: Re: Pgadmin 4 cannot add or modify line in a view To: Usman Khan Cc: pgadmin-hackers@lists.postgresql.org, pgsql-sql@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000070b2930619afa280" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000070b2930619afa280 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 UPDATE I checked both source tables and they are well updated. The reason why Pgadmin locks the array may 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 view. Thanks On Thu, May 30, 2024 at 5:52=E2=80=AFPM Usman Khan wrote= : > > Can you please elaborate your requirement a bit more? > The result grid is usually non editable for views. You can edit table dat= a > to reflect values in view. > > Note : adding pgadmin-hackers for more guidance. > > > On Thu, May 30, 2024 at 7:25=E2=80=AFPM intmail01 w= rote: > >> 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 line= 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 >> > --00000000000070b2930619afa280 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I read the PostgreSQL manual and view can be modified= if some rules are respected. My query is very simple and follow rules : SE= LECT * FROM thePartionedTable
When I run code with INSERT and= UPDATE clause then it work fine.
In fact the view comes from a p= artitioned table. After an INSERT or UPDATE I checked both source tables an= d they are well updated.

The reason= why Pgadmin locks the array may=C2=A0 come from the fact there is no defin= ed primary key. My partitioned table have primary key.
I do not h= ave 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 <umk555@gmail.com> wrot= e:

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
--00000000000070b2930619afa280--