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 1hsq1S-0002J6-OX for pgsql-admin@arkaria.postgresql.org; Wed, 31 Jul 2019 14:56:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hsq1R-0002N3-Jc for pgsql-admin@arkaria.postgresql.org; Wed, 31 Jul 2019 14:56:09 +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 1hsq1R-0002Mv-AN for pgsql-admin@lists.postgresql.org; Wed, 31 Jul 2019 14:56:09 +0000 Received: from mail-wr1-x42c.google.com ([2a00:1450:4864:20::42c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hsq1O-0003Zt-Bk for pgsql-admin@lists.postgresql.org; Wed, 31 Jul 2019 14:56:08 +0000 Received: by mail-wr1-x42c.google.com with SMTP id p17so70013776wrf.11 for ; Wed, 31 Jul 2019 07:56:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language; bh=PZr2RUiVM6Ejj488a5o+AmiRm+wOR2umXAwn1DC9ScI=; b=R+AcU9zd+htpoacqZi2jL1FJLSWGlV1GfVVHkKEklFGn7sw4Ic6YoKn8ILdLZ6W6Cj AuBSAqv+Z8DonMNM72Re/6B1W37eWKxeIjuSr4aYb6rx3uNWxBOuoouYcj8Tm/ej6iCW AZCooAxwtrih9C2rsrA5bNuoAOfHesFRZpaSr2DXUcwp/NSRuPHI9GdNjMKF3bwZiVgi o5mdwbEmjKB9SUH7c6GhpkCzGmKv+1+Mu/Gj8vmJyCOhEhNzkFImGRCunzEaejS4am2k cunMk121bPNxx32hWFSjZW26+Ms9s3tSRpphQsfzBE888rC4mSLd6vsU4I0miiS0Y5uE b40Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language; bh=PZr2RUiVM6Ejj488a5o+AmiRm+wOR2umXAwn1DC9ScI=; b=VEcalpdbCYp6jUVMz0MF4Kro+T0gDueYjZXMxcu+UXLbML9YyT7U9Z/92BgoA3VLUp fvVwUiCFlvOpQkDbdegF2ScqFieryLuZjl2J+CCURfzusPblCxBu5qqDOUaDikWsXGJI bKOJTn1Q1Ovu7PlWdWe9GLxSOLfQIX/BeVuYIOhnr3sIoraUIw5WX2TsQKlpYVK575JK EN2iMOfRxfY1cf+l0/kKQlVJ53lynzIzYKxFmuWqC4qcaGuQDsgeOSByX0+61rsZzN1M OI0tacmYlgqeKe0TZEI/I4kuR1u2KAbE/LWjFu/Wx7+/M6O4byd4ojGut963NJCPuV0i V3Iw== X-Gm-Message-State: APjAAAUGDVreF0GjicT8LsikXrqNRHa02MzC5avonHyJ1iPDyp4LPjvj 3pyfi9eqTtG9QyXnESH6L31wkSMlUoo= X-Google-Smtp-Source: APXvYqx7SEmezMVpflKANztcJcWxmkjVvKVZ9zrzAuj/Z+js0sKiNDQ1zmGgftxJOh5ZzQM47WPEYw== X-Received: by 2002:a5d:6182:: with SMTP id j2mr86869311wru.275.1564584963861; Wed, 31 Jul 2019 07:56:03 -0700 (PDT) Received: from [192.168.0.210] (melany.rs. [178.254.155.58]) by smtp.gmail.com with ESMTPSA id t1sm82108171wra.74.2019.07.31.07.56.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jul 2019 07:56:03 -0700 (PDT) To: pgsql-admin@lists.postgresql.org From: Milan Oparnica Subject: Search database objects Message-ID: Date: Wed, 31 Jul 2019 16:56:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------35EA234140DAB88FD12288E6" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------35EA234140DAB88FD12288E6 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, I like the fresh and modern approach that pgAdmin4 offers, updating instantly when new versions pop-up praying to find few options I still miss from pgAdmin3. Search database objects =============== I'm sure this tool will put a smile on many faces. Although not perfect, the 'Search' option in good-old pgAdmin3 is still superior to the 'browser-based-search' we have now. It takes a lot of time to: 1. Expand the database tree 2. Expand the desired schema (and you have to know which one exactly) 3. Expand the proper node (tables, views, functions...) 4. Search with the browsers tool - hoping from one partial-result to another trying to spot the right one... When collections hold thousand items it takes too much efort. Are there any plans to add the 'Search tool' in pgAdmin4 ? Best regards Milan Oparnica --------------35EA234140DAB88FD12288E6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Hello,

I like the fresh and modern approach that pgAdmin4 offers, updating instantly when new versions pop-up praying to find few options I still miss from pgAdmin3.

Search database objects
===============

I'm sure this tool will put a smile on many faces. Although not perfect, the 'Search' option in good-old pgAdmin3 is still superior to the 'browser-based-search' we have now.

It takes a lot of time to:

  1. Expand the database tree
  2. Expand the desired schema (and you have to know which one exactly)
  3. Expand the proper node (tables, views, functions...)
  4. Search with the browsers tool - hoping from one partial-result to another trying to spot the right one...

When collections hold thousand items it takes too much efort.

Are there any plans to add the 'Search tool' in pgAdmin4 ?


Best regards

Milan Oparnica

--------------35EA234140DAB88FD12288E6--