Skip site navigation (1) Skip section navigation (2)

Re: Query tool: Autocompletion

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>,"Magnus Hagander" <mha(at)sollentuna(dot)net>
Cc: <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Query tool: Autocompletion
Date: 2006-01-26 08:40:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de] 
> Sent: 26 January 2006 00:06
> To: Magnus Hagander
> Cc: Dave Page; pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] Query tool: Autocompletion
> I've spent several hours now to get the beast compiled, still no go. 
> It's a nightmare I don't like to spend more time on.

Hmm, I got it going in 5 minutes in VC6. Works quite well.

> Dave, if you succeed hacking something workable that doesn't 
> try to call 
> more core pgsql includes from somewhere (!), commit it. Note: pgsql 
> copied stuff should go to src/db, not utils.

Well, I can certainly commit what's there fairly quickly.

> Actually, I doubt that the psql way is desirable at all. Instead of 
> constantly accessing the db for completion candidates, using 
> pgAdmin's 
> object tree as cache should be the way to go.

That's a good point. Magnus, any thoughts on doing it that way?
Shouldn't be too hard to swap out the queries for scans of the tree.

Mind you, the downside of that is that tab complete would essentially
have to build large chunks of the tree on databases that might not even
be connected in response to random typing in the query tool. Whilst it
seems a nice idea to use the tree objects as a cache, it could have some
pretty nasty side effects.



pgadmin-hackers by date

Next:From: Dave PageDate: 2006-01-26 08:50:09
Subject: Re: RE : [pgadmin-support] pgAdmin website translations
Previous:From: Chris LeahyDate: 2006-01-26 06:47:55
Subject: Small problem compiling

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group