RE: v3.3 Auto complete broken

From: "Hibbard, Brandon" <Brandon(dot)Hibbard(at)zimmerbiomet(dot)com>
To: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
Cc: pgAdmin Support <pgadmin-support(at)postgresql(dot)org>
Subject: RE: v3.3 Auto complete broken
Date: 2018-10-17 12:52:01
Message-ID: 9601028ae3ab47df9c6c50dc448c2214@SBDEXDAG09.zmr.zimmer.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hello Akshay and pgAdmin support,

I am on version 3.4 now, and the auto complete is listing the tables in the schema, but it is not listing the fields in the table. Is this still an open bug?

I have also noticed an odd formatting behavior when there are nested functions. An example is Upper(trim(b.source)). At the end of this line, if you enter down, the auto indent is way off and continues to be for the following lines. If you add a space between the last two parenthesis like Upper(trim(b.source) ), the auto indent works as expected.

Thanks,
Brandon

From: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
Sent: Monday, September 10, 2018 12:05 PM
To: Hibbard, Brandon <Brandon(dot)Hibbard(at)zimmerbiomet(dot)com>
Cc: pgAdmin Support <pgadmin-support(at)postgresql(dot)org>
Subject: Re: v3.3 Auto complete broken

Hi Brandon

RM 3630 has already been there and I have sent the patch on pgadmin hackers where objects belongs to schema other than pg_catalog and public are not listed. You can apply that patch and test it.

On Mon, 10 Sep 2018, 21:26 Hibbard, Brandon, <Brandon(dot)Hibbard(at)zimmerbiomet(dot)com<mailto:Brandon(dot)Hibbard(at)zimmerbiomet(dot)com>> wrote:
Hello,

I installed pgAdmin 4 v3.3 today and autocomplete isn’t working correctly. It does not list the tables in a schema or the fields in the table. Is this a bug or have I done something wrong?

Thanks
Brandon

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Akshay Joshi 2018-10-18 06:26:55 Re: v3.3 Auto complete broken
Previous Message Khushboo Vashi 2018-10-17 03:44:39 Re: Problem with encoding (display wrog characters)