Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q9jTT-00048Y-2M for pgadmin-hackers@arkaria.postgresql.org; Thu, 15 Jun 2023 09:41:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q9jTR-0001u1-9G for pgadmin-hackers@arkaria.postgresql.org; Thu, 15 Jun 2023 09:41:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q9jTQ-0001ts-Bz for pgadmin-hackers@lists.postgresql.org; Thu, 15 Jun 2023 09:41:01 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q9jTM-002K27-O0 for pgadmin-hackers@postgresql.org; Thu, 15 Jun 2023 09:40:58 +0000 Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-977ed383b8aso247882966b.3 for ; Thu, 15 Jun 2023 02:40:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1686822055; x=1689414055; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=y2zadKuic33Wa+ajSE+Q41yQUO4qmrFIa1g9uXOfsvA=; b=MO9ElbPlQKPbhQRc1WoJMUO++MeEivbOqLTTNW1uPqk6AiYV+fiZhKmZoG6bnb9Vip PH8otv6J4VI+UGQKKQ8JaV7tIeKqkMYPyyjX1JtfNeqkJm0DYzWfysgiNp7RP9D7y1zX BgOq3dzErMp94nWQtnGsJl4Xp7KkgXC2MfIttlUepUCsjQ+DRPEQptlL7NAIV++Q8JAR 8ukflUEF9qlYZb1XQqlIF6ZOZvbNLPflLbOkOyOUB9Pi4EqmU6GlFpHAjcEgNJNlh9V2 aQspKcyHkkZji7Uvu7EuTlpHuA1/IDDPEQ+Ts2KtmmTKC7Lti0kQYXXI++KsbBdxsfqD xxow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686822055; x=1689414055; 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=y2zadKuic33Wa+ajSE+Q41yQUO4qmrFIa1g9uXOfsvA=; b=blkhnmdDgaRfHP71TU1zOAe69lFZnIGc/6mQF5kBqz2zJEGxmEftQeyR/WzzK9uRbD HFwMHr+BCPCoIF4k9cYoQCEoDg/4fpP7NfbjDSt2/jrwDbKDQk3mLoBWqb6wJkmqTexx n4qTxh/yjlLs3/9NGX+IaO68fGQaeD9yYq6yDnyXoJtuOZAAZLDx44IRCvpnRzCVzSKn BhBDmPFpewKZNWln8saZrZwsFBXRoIl0HbZZZn46o7gOLYy6WJQBYmcoMSvBLKIFg3ml 7vQ/hlllM8mMLcraS2Oei0Gib2nhD8mYQgLUM785kDOTB2TQDWLrHgol3t7/lw5uKzGb 2PxA== X-Gm-Message-State: AC+VfDxFE2MzZc2I9DjmhkGM/DC61N8/079lCBG/J/NzXxPtbH5tBrGK /rs+wnPyeOuzmEicxftcGDojuutdYOoiJsxCImqCPg== X-Google-Smtp-Source: ACHHUZ5q1SoMXB5TcwUu2OEuxOwPzWr+rs9yIdrf3W8Tl0dqIJyCiDF48tQkQmY+fktpAofVx/lKE389/MQO5oLBnTE= X-Received: by 2002:a17:907:3f9d:b0:982:9dc1:a434 with SMTP id hr29-20020a1709073f9d00b009829dc1a434mr1397036ejc.19.1686822054991; Thu, 15 Jun 2023 02:40:54 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Thu, 15 Jun 2023 10:40:43 +0100 Message-ID: Subject: Re: Required inputs in issue #6138 To: Nikhil Mohite Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000632c8105fe27dd62" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000632c8105fe27dd62 Content-Type: text/plain; charset="UTF-8" On Wed, 14 Jun 2023 at 13:43, Nikhil Mohite wrote: > Hi Hacker, > > I am currently working on issue #6138 > , which was fixed > earlier but the fix was not correct so working on it again. > Steps to reproduce the issue: > 1. Open *View/Edit Data *for *table1* > 2. Open the PSQL tool delete the same *table1 *and recreates the same > name table *table1* and try to re-execute the query from the > already opened *View/Edit data *panel. > 3. pgAdmin throws an error in the Messages tab *List index out of range *(pgAdmin > query to get table columns from Postgres based on *table oid* which was > deleted and the return result is empty which is not handled in pgAdmin)*.* > > Approach to fix this issue: > 1. If the user re-executes the query from already opened *View/Edit data* we > should fetch the table details by using *schema and table name (not using > table oid)* and show the newly created table records in the result. > (This will only fix an issue with *View/Edit Data *however if the user > switches to properties or some other panel it user will still get an error > notification with content *"could not find the specified table."*) > I think this is fine. The View/Edit data window shows the query with table/schema name after all, so the user should expect it to work. -- Dave Page Blog: https://pgsnake.blogspot.com Twitter: @pgsnake EDB: https://www.enterprisedb.com --000000000000632c8105fe27dd62 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable



-- =
--000000000000632c8105fe27dd62--