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 1ieFlU-0003Pd-Nv for pgadmin-hackers@arkaria.postgresql.org; Mon, 09 Dec 2019 09:55:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ieFlT-0001N2-98 for pgadmin-hackers@arkaria.postgresql.org; Mon, 09 Dec 2019 09:55:39 +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 1ieFlS-0001MJ-Ve for pgadmin-hackers@lists.postgresql.org; Mon, 09 Dec 2019 09:55:39 +0000 Received: from mail-ed1-x542.google.com ([2a00:1450:4864:20::542]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ieFlQ-0001TA-95 for pgadmin-hackers@postgresql.org; Mon, 09 Dec 2019 09:55:38 +0000 Received: by mail-ed1-x542.google.com with SMTP id cy15so12136894edb.4 for ; Mon, 09 Dec 2019 01:55:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0gT+1i7/tW/Rv6BD2CO8oluNIN8J6QoqWm4Arhhz/V0=; b=JdbhsWs+zB6KGNzvLccKLy/XuOTj994Q8B3/eyGVr8Z5Lu5s+4Bw9Qe5dtYKRrbPmR x2ukpBFGslhrBpZQWyYj2TqS3gumTsyVHwSOkyUS2ILmXtF2Nnl3shFoOFECWPHP0pbM KN/Wa5jsHRyNu3sZDnbGftUNngzle/gPBtEn4wUXt51l3q1CdEBxA081lcwRqQ7ZrKYt 0AS8m6vMlq6dyBtGpVD0zSBC7Cd2kplY2ZptOPbTBfEJuvEIP4+34mlfBvFVMFX9o2Ol LACdwUuMzApFDrSaFc+CFDbyGBDhNoSmwHDSdqDuie1fuRLFnuZrfoEzOqRJ0jw3UyfK kDjg== 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=0gT+1i7/tW/Rv6BD2CO8oluNIN8J6QoqWm4Arhhz/V0=; b=iWD23Vay1jy6DR/uVrlTh7xanniXmWvO0Nbpz+3CpZq/X+b7p2njIKhl3hSWbvDFNx F/aMX6hhispV1z28mLoGZiSmeSjF4gLGHZh1DrM7QDpal2EjKhuGcFNssah/MjqyumFT 8PzPpjZqIg223ZclMJfUSshPRDoPC/SjXxRi/nNBSPny0N394B/n22Lck/gEpEh/Ct7y 5P0tG3tCEfKqGIp5dmwRD/eTEcovmkmdQqD15QkrXJuiVlzQrK77nMwkbI09Ydf63oM1 FcTjYDGMZzbWQNpdrvofW+XafVrUIF/oShwTwDSHgFPN7yiOtcnRBJ2SeKv5f2Q7UgMb xeag== X-Gm-Message-State: APjAAAUOUckHFbABUOM8C+LaiAwFH7S/nKg5YILCZx2Y4vO34Es54ge4 HH3WJZDGPMJfLcFk4PLKgo6JtQG/xyIFIjJvSoBdNs2mI52NDdDEqntkdtWfYwwxWMKvmHx7DF/ 9Ual3qfKLsjPYru5n4gjrdhfpFrL8Vlf6z+VhshbUgZ86M1SRebiXBHIK8UyyuOQek4w7/FbKTq gp142yK70pHXwqvWlQebr1q+yOLNikC1zou/L2lNpxl4bs9L+A5sw= X-Google-Smtp-Source: APXvYqxvYLsKl8XjCjry3yXY+HjJELFRaGwuAtKL5yaB05v9rFCOaI1/g9X4TtDQdYvu5v/7013vDCYD2fM/QCt50N0= X-Received: by 2002:aa7:d48d:: with SMTP id b13mr30906372edr.246.1575885334962; Mon, 09 Dec 2019 01:55:34 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Aditya Toshniwal Date: Mon, 9 Dec 2019 15:24:58 +0530 Message-ID: Subject: Re: Re : [BUG #4943] To: Karan Takalkar Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="0000000000009903710599426512" X-CLOUD-SEC-AV-Info: edb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000009903710599426512 Content-Type: text/plain; charset="UTF-8" ++pgadmin-hackers Hi Karan, It is good to know that you're contributing. I would suggest {server name}/{db name} as name instead of did is better for UX. You can get the db name from conn object and server name using the sid (refer - web/pgadmin/browser/server_groups/servers/__init__.py) On Mon, Dec 9, 2019 at 3:11 PM Karan Takalkar wrote: > Hi, > > I have been working on #4943 ("Database connected" success message itself > is not enough) added by you on pgAdmin4 issues. > I want to know what details of database should be included in success > message.(i have added 'did') > > The success message can be modified by altering json response in the > connect method in file > PGADMIN_SRC/web/pgadmin/browser/server_groups/servers/databases/__init__.py. > please have a look at the screenshots attached. > > original: > info=_( "Database connected.") > new: > info=_("Postgres version/{0} Database connected.".format(did)) > > Regards, > Karan > -- Thanks and Regards, Aditya Toshniwal Sr. Software Engineer | EnterpriseDB India | Pune "Don't Complain about Heat, Plant a TREE" --0000000000009903710599426512 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
++pgadmin-hackers

Hi Karan,

It is good to know = that you're contributing.
I would suggest {server name}/{db name} as na= me instead of did is better for UX. You can get the db name from conn objec= t and server name using the sid (refer -=C2=A0web/pgadmin/browser/server_gr= oups/servers/__init__.py)


On Mon, Dec 9, 2019 at 3:11 PM Karan Ta= kalkar <karan1533os@gmail.com> wrote:
Hi,

I have been working on #49= 43 ("Database connected" succe= ss message itself is not enough) added by you on pgAdmin4 issues.
I want to know what details of d= atabase should be included in success message.(i have added 'did')<= br>

The success message can be modified b= y altering json response in the connect method in file PGADMIN_SRC/web/pgad= min/browser/server_groups/servers/databases/__init__.py.
<= span style=3D"font-weight:normal">please have a look at the screenshots att= ached.

original:
info=3D_( "Database connected.")
new:
info=3D_("Postgres version/{0= } Database connected.".format(did))

Regards,
= Karan


--
Thanks and Regards,
Aditya Toshniwal
Sr. Software Engineer |=C2=A0EnterpriseDB In= dia |=C2=A0Pune
"Don't Complain about Heat, Plant a TREE"
=
--0000000000009903710599426512--