Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hqywN-0003vW-Pv for pgadmin-hackers@arkaria.postgresql.org; Fri, 26 Jul 2019 12:03:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hqywM-0000W3-BM for pgadmin-hackers@arkaria.postgresql.org; Fri, 26 Jul 2019 12:03:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hqywL-0000S7-TQ for pgadmin-hackers@lists.postgresql.org; Fri, 26 Jul 2019 12:03:14 +0000 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hqywJ-0005MF-M2 for pgadmin-hackers@postgresql.org; Fri, 26 Jul 2019 12:03:13 +0000 Received: by mail-wr1-x441.google.com with SMTP id r1so54168592wrl.7 for ; Fri, 26 Jul 2019 05:03:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r+tupBwlYarxNE0A3QCcfPDnJjU0exG2jTO9hv2xnSE=; b=dBEN3MRSjOA27XamaS5qXumkqFqj7cVlLrSWZL8rIixLKXJbc6Jsxp2Nnaayvo6Vij Y5mc6jxsbsdWgTKNlQ8ku9B2FQuMuc+eU8LfWrpGPkv/pmrOnsprmHpTNxGLJlCaorEr vLE3XvCBYcA/uoLhIz8mCgnhevEFLEi3WgdaKytc6ErJ2Tswpf5TVp7TfZ37V2/zqXGW CNNZVLUCLwAyfZDob9cdWqvLW3TFfCrrBzUaM49WUPVVeI4TQqjlEbA3TWHOR6hiM6k1 vhlFpTv+F7YDQSBe26zNdPdX+mIzhX6dJy47iP4MFcB33eJNLz3LGpbEU7EKF8q0Sc7g X/Zg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r+tupBwlYarxNE0A3QCcfPDnJjU0exG2jTO9hv2xnSE=; b=j4qnLkda2NxuNCiGORpC2268g1FNoD5Kc4Uibzki/jmf+Us4gQa1ewUMaFLeaIYGAt x3hbcoVddsXFL+vc/qt1kj2cIOpzSjv7lSZGuiY7K6mkco3HwVGTYq4e+xQBGECLm5er /Zz5zfOo4GtcnbMziTRx11YBf9IfKt3Gmk6MtapLvOKjVOrkrmb7cT4cI+AMJWF/rqjC 0t3tMnp/UVIunDEQrxzqa5zRdqF7ODQt68Juo+/pWsudGJ/CmY0DITeTQ4Y1b97ox7tA IowjxI30wT+xuZmOntXGpvlEdQf8DSXIi9VHCrz6FcPGaarGKmJetWpcBO/mA0WIsxcE Funw== X-Gm-Message-State: APjAAAXLNVIPty3QE2PCqgk4DgD2uyFmQhzD0vnEWqNjEzLLPd/U5Bgx AlgdexFTsSpxeuD7phDRLG/VeL0adw+23xer+dpuoA== X-Google-Smtp-Source: APXvYqzaR446yipt30O22RYV0MgMi/aawXSL+nFTMQ7m2HkIybLzq9zGX+bOo7f9cUkjG7mklIVpkXdGFVLgb0LDkQ0= X-Received: by 2002:adf:f104:: with SMTP id r4mr9905580wro.140.1564142589366; Fri, 26 Jul 2019 05:03:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Fri, 26 Jul 2019 13:02:56 +0100 Message-ID: Subject: Re: [GSoC] Support editing resultsets from tables with OIDs To: Yosry Muhammad , Akshay Joshi Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000006aec3a058e945379" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000006aec3a058e945379 Content-Type: text/plain; charset="UTF-8" Akshay; can you take a look at this and commit if appropriate please? I'm somewhat busy at the moment :-( On the subject of the regression test - I assume at one point the messages window was including the command tags in it's output. This failure would indicate we broken that. Anyone got any ideas how that happened? On Thu, Jul 25, 2019 at 1:01 PM Yosry Muhammad wrote: > Hi, > Please find a patch attached to add supporting of resultsets from tables > with OIDs as updatable resultsets (with updated test cases and docs) - this > is a part of a GSoC project. Please review ! > This patch also includes a small refactor of the previous patch and a > small bug fix that occurred when the query resultset had no rows but was > updatable (row additions were not permitted, although they should be). > > > On a different note, one of the feature tests fails (on master), probably > due to a small typo. In query_tool_tests.py this function call: > > self.page.find_by_xpath( > '//div[contains(@class, "sql-editor-message") and ' > 'contains(string(), "CREATE TABLE")]' > ) > > on lines 371-374 produces an exception that the element cannot be found, > this is probably due to the fact that the message returned by the query > executed before this call does not contain the string "CREATE TABLE". Just > letting you know about this. > > Thanks and regards! > -- > > *Yosry Muhammad Yosry* > > Computer Engineering student, > The Faculty of Engineering, > Cairo University (2021). > Class representative of CMP 2021. > https://www.linkedin.com/in/yosrym93/ > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --0000000000006aec3a058e945379 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Akshay; can you take a look at this and commit if appropri= ate please? I'm somewhat busy at the moment :-(

On t= he subject of the regression test - I assume at one point the messages wind= ow was including the command tags in it's output. This failure would in= dicate we broken that. Anyone got any ideas how that happened?
<= br>
On Thu,= Jul 25, 2019 at 1:01 PM Yosry Muhammad <yosrym93@gmail.com> wrote:
Hi,
Please find a = patch attached to add supporting of resultsets from tables with OIDs as upd= atable resultsets (with updated test cases and docs) - this is a part of a = GSoC project. Please review !
This patch also includes a small re= factor of the previous patch and a small bug fix that occurred when the que= ry resultset had no rows but was updatable (row additions were not permitte= d, although they should be).


On= a different note, one of the feature tests fails (on master), probably due= to a small typo. In query_tool_tests.py this function call:
self.page.find_by_xpath(
'//div[contains(@class, "sql-editor-mess= age") and '
'contains(string(), "CREATE TABLE")]'
)
on lines 371-374 produces an exception that the elem= ent cannot be found, this is probably due to the fact that the message retu= rned by the query executed before this call does not contain the string &qu= ot;CREATE TABLE". Just letting you know about this.

Thanks and regards!
--=C2=A0

=
Yosry Muhammad Yosry<= /i>

Computer Engineering student,
The Faculty of Engineering,
Cairo University (2021).
Class repres= entative of CMP 2021.


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

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL = Company
--0000000000006aec3a058e945379--