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 1hmpNl-0002tf-Ta for pgadmin-hackers@arkaria.postgresql.org; Mon, 15 Jul 2019 01:02:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hmpNk-0002UF-P9 for pgadmin-hackers@arkaria.postgresql.org; Mon, 15 Jul 2019 01:02:20 +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 1hmpNk-0002U8-IU for pgadmin-hackers@lists.postgresql.org; Mon, 15 Jul 2019 01:02:20 +0000 Received: from mail-qk1-x741.google.com ([2607:f8b0:4864:20::741]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hmpNi-00054r-4S for pgadmin-hackers@postgresql.org; Mon, 15 Jul 2019 01:02:19 +0000 Received: by mail-qk1-x741.google.com with SMTP id g18so10439606qkl.3 for ; Sun, 14 Jul 2019 18:02:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=nT7BNsfadUHau/x9d3bPvGNTdxN+RPaeHvQTkT823yU=; b=lC8vTiOoavr8Rd/Hhe03Y1J3SCQCmuGoyo7vyH36gopLgzDgnp4mYgFU2s/jUx0Pef JEOjJ/2gI/H1AVbX87+ykShr/QuFymaJ0dGIcSovznOztja5cM3w1O/e1YvXgmjyxlqJ 8wEtNHa0vetGc5yxrr1vnYAyFR7eImUdWo+ix2vRaE0ym89wAWvwL5tpKyY5X5ea7yu1 ZR8hkp8+jsGZPUm+YOqYSU1zGoeEi2dQc2p7Wl1dVpHYU9heFzhFpP3kPa8ZLh0wfmbh HkSicRBHthHUFWx/XCl1t3a9/wb4xlWsEF1J8DGtixwe5bBVV8PbwNyqkMVQBxi3cdvM v4KA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=nT7BNsfadUHau/x9d3bPvGNTdxN+RPaeHvQTkT823yU=; b=bvJVKDfgPZHFzPFppflNqORu82tYKbRmxmaMUhZ3WrjzB+dwSTA5QqSGXnRpUecLaq IXceRMub4kQDPfdLSz4UCIy3ETCdV/A+sQLqHNGaPCe5YXmps91meJkSomDSt9Xxg15+ dShZhUNr0nBOrrEYStenwPZlzcxIAW+vGJokZt6PKaYy+V1nKIWYupjNVtJyLtkJiTN7 dNq7LdpdcsQTWUlsZX5a75Wuh7vjY9eN+dpKKTcncyf2sZQPqIZawxWtzqWKpNq37tew FT9x5ayakgy0OY2CzZAu6qOchVVfom97XA671r5D7MFZaum4EgzBhrtyLslWQbsWNQEr ug/A== X-Gm-Message-State: APjAAAXfTmoI4JSKIhKv5Rhj4OIB1XsgN1SO6cM9mer0WFR63v7oAaU8 54SRczls7DwGmbe5wpq8GEKIVcmS9rzjlZG2ZMw= X-Google-Smtp-Source: APXvYqyM6YenXnAh3nKWFx8c4/lMIJfbSQav/69qcAhJMY/5Mp5yy4K3slQf03xx/iGx014wFxOTzx2rTwpEthKEYPM= X-Received: by 2002:a37:a80d:: with SMTP id r13mr7503200qke.209.1563152536630; Sun, 14 Jul 2019 18:02:16 -0700 (PDT) MIME-Version: 1.0 From: Yosry Muhammad Date: Mon, 15 Jul 2019 03:02:04 +0200 Message-ID: Subject: [GSoC] Ideas for the remaining of the project To: Dave Page Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000acfb10058dadcfb0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000acfb10058dadcfb0 Content-Type: text/plain; charset="UTF-8" Hi Dave, The core patch for this project is being finalized and I am unable to work for the current few days due to issues mentioned in the previous email. Therefore, I have been thinking of what can be done in the project after this patch is done. Below are the features I have been thinking of with a short description (ordered by priority in my point of view): 1- Supporting tables that have OIDs rather than primary keys (I have a bit of research to do about OIDs and how they work). 2- Modifying the way table information is sent from the backend, and the way they are processed in the frontend. This will include (but is not limited to) modifying the columns info sent to the frontend to include: - Whether the column is a primary key (instead of matching by name at the frontend). - Whether the individual column is editable. This means there could be editable resultsets with read-only columns. It will allow for supporting a wider range of resultsets, such as: queries selecting some columns from a table in addition to an aggregation performed on one or more of the columns, queries with renamed columns, etc. It will also include modifying how columns info is handled in the frontend. 3- Mogirfying queries generated by pgAdmin during saving data changes to be able to display them in a meaningful way to the user. Moreover, a checkbox/preferences option is to be added to enable/disable showing them in the query history (to be discussed further upon implementation). This will involve modifying the cursor and connection wrapper classes in the backend to add a mogrify function wrapper in addition to other changes throughout the code. Please let me know what you think of this. Looking forward to feedback, suggestions and comments. Thanks and regards. --000000000000acfb10058dadcfb0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Dave,

The= core patch for this project is being finalized and I am unable to work for= the current few days due to issues mentioned in the previous email. Theref= ore, I have been thinking of what can be done in the project after this pat= ch is done.

Below are th= e features I have been thinking of with a short description (ordered by pri= ority in my point of view):

1- Supporting tables that have OIDs rather than primary keys (I have a = bit of research to do about OIDs and how they work).

2- Modifying the way table information is sent= from the backend, and the way they are processed in the frontend.=C2=A0

This will include (but is = not limited to) modifying the columns info sent to the frontend to include:=
- Whether the column is a primary key (instead of m= atching by name at the frontend).
- Whether the indi= vidual column is editable. This means there could be editable resultsets wi= th read-only columns. It will allow for supporting a wider range of results= ets, such as: queries selecting some columns from a table in addition to an= aggregation performed on one or more of the columns, queries with renamed = columns, etc.

It will al= so include modifying how columns info is handled in the frontend.

3- Mogirfying queries generated b= y pgAdmin during saving data changes to be able to display them in a meanin= gful way to the user. Moreover, a checkbox/preferences option is to be adde= d to enable/disable showing them in the query history (to be discussed furt= her upon implementation). This will involve modifying the cursor and connec= tion wrapper classes in the backend to add a mogrify function wrapper in ad= dition to other changes throughout the code.

Please let me know what you think of this. Looking for= ward to feedback, suggestions and comments.

Thanks and regards.

--000000000000acfb10058dadcfb0--