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 1s2SjC-003ChV-67 for pgadmin-hackers@arkaria.postgresql.org; Thu, 02 May 2024 09:27:46 +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 1s2SiB-00Gzx9-L2 for pgadmin-hackers@arkaria.postgresql.org; Thu, 02 May 2024 09:26:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s2SiB-00Gzwy-8U for pgadmin-hackers@lists.postgresql.org; Thu, 02 May 2024 09:26:44 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s2Si6-0013oy-BU for pgadmin-hackers@postgresql.org; Thu, 02 May 2024 09:26:42 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-23d3afdcd71so981879fac.1 for ; Thu, 02 May 2024 02:26:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1714641997; x=1715246797; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Edjp+DqygDqkZoTUa2GMVUxN/YQ1RpDreBEgAc1kk1I=; b=WBhbAwq41L1ivU4QkN4pfEwTKrekOOi4WVG24HwX2KH/qbcE7g4Ghh/ovJGrBdS3DQ KgNVx9OeIE7nfN5i+fZybJEB/FgrcMrU+ZH10/EVQZwhkkemg4kYtJQR+Ll/qcKlhqBI 730Jnh2KGIp2n3q/aEifu5Q/MXgHQ0g+myQqSrCJaMmHQzRF5x0GT/jd/fcIIarqt96L AgTgQ3GUmYtSX3QksTs+mbgT0DUyXlJDNRPiU3Rrc93HTgBn+Qk3OlhTj8jaXRC7wKNE muiKaVFEsH4dC3DyxGZ8T5C4kG+0yL5WDhUVIK6UIpLBycuIiZfXaAM4xb+PVXfM0cIX 8fVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714641997; x=1715246797; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Edjp+DqygDqkZoTUa2GMVUxN/YQ1RpDreBEgAc1kk1I=; b=mQWhsCHUVlS8GG94GKJ/8ST4pyQ2cb8Usg9/l1RuAZN3nPzhc/aPds+38efVUlBdih bpDisWKqFmNBdhUkuwPLie2xQNkc9CPO6hHR2UHlsZw0zykpMlNkvughFf5bv7maq16D nKdAH/16gJXS+ux7ohEz2vSgUImunIuIkeFFdnB+DOFwckLukOS40+MklGZhBxgCpbYZ oIMJFFLMD0+IREmjkHCqHoWGrZpPUWV61UYdXbgBK+owo5202fjX4Sw04zougaVIp0QX 0Q85OGWUZEbB5j3I2uRpO9W6tsSrL5+MCU54hFMdLAO3oWHCxWMBV99Z9iFviMdY+efY 34TQ== X-Gm-Message-State: AOJu0Ywrxl5hrEV1LMFQyGTKQRxLID5nnXCEumo9VCNo7l28M0lFB1Pz RmoqK+yHuZKBx9SXs3Uwr9tha3l2Jxwr1rGDvn44c8FtiNsX8v5JZ3UvSx2dx1+mfCbC3AWTBHR iuQBqtTKt9yVZPuCkfz9hPymI2oF707fA6xgRllT7NhG4hSQM9Qjf X-Google-Smtp-Source: AGHT+IHoy8i3GlU2nzTbIc20CJBHKgfrvCUBs9XMlk+QnumugHqrO5w91Wmp3vVWFgV1hLrpOVTs+RgDy4j6+6eKblQ= X-Received: by 2002:a05:6870:5248:b0:23b:b0fd:47f4 with SMTP id o8-20020a056870524800b0023bb0fd47f4mr5708039oai.18.1714641997169; Thu, 02 May 2024 02:26:37 -0700 (PDT) MIME-Version: 1.0 From: Rohit Bhati Date: Thu, 2 May 2024 14:56:26 +0530 Message-ID: Subject: Proposal for ticket No :- #7411 To: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="00000000000028a7530617753340" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000028a7530617753340 Content-Type: text/plain; charset="UTF-8" Dear Team, I hope this message finds you well. I'm reaching out to discuss a proposed enhancement for our project regarding the formatting of deletion actions. As I've working on GitHub ticket #7411 , there's a suggestion to introduce consistent formatting specifically for the "Delete database force" action. However, upon further review, I believe extending this formatting to other deletion actions could significantly improve user clarity and experience. Here's a summary of the proposed changes: - Delete database and Table: Click to delete the currently selected object from the server. (use the same code, if one is made bold, then both will become bold) - Delete database force: Click to delete the currently selected database with the force option. (as per the original suggestion) - Delete table cascade: Click to delete the currently selected object and all dependent objects from the server. - Delete Truncate: Remove all rows from the table. - Delete Truncate Cascade: Remove all rows from the table and its child tables. I'd like to gather your thoughts on extending this proposal to include all mentioned deletion actions. Please take a moment to review the proposal and share your thoughts, concerns, or alternative suggestions and I look forward to hearing from you soon. Best regards, Rohit Bhati --00000000000028a7530617753340 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Dear Team,

I hope this message finds you well. I'm reaching = out to discuss a proposed enhancement for our project regarding the formatt= ing of deletion actions.

As I've wo= rking on GitHub ticket #7= 411, there's a suggestion to introduce consistent formatting specif= ically for the "Delete database force" action. However, upon furt= her review, I believe extending this formatting to other deletion actions c= ould significantly improve user clarity and experience.

Here's a summary of the proposed changes:

  • Delete database and Table: Click to delet= e the currently selected object from the server. (use the same code, if one= is made bold, then both will become bold)
  • Delete= database force: Click to delete the currently selected database wit= h the force option. (as per the original suggestion)
  • Delete table cascade: Click to delete the currently selected obj= ect and all dependent objects from the server.
  • De= lete Truncate: Remove all rows from the table.
  • Delete Truncate Cascade: Remove all rows from the table and its= child tables. I'd like to gather your thoughts on extending this proposal to include = all mentioned deletion actions.
    Please take a moment to review the propo= sal and share your thoughts, concerns, or alternative suggestions and I loo= k forward to hearing from you soon.

    Best regards,
    Rohit Bhati

--00000000000028a7530617753340--