Re: how to disable auto-completion

I would like to request that PgAdmin do a better job at auto-completion as well.<br />I don't use it now since what I
reallyneed is help with the columns, more than the tables. <br />The tables are useful, but often I know the table
namesbut can't remember the column names and auto-completion on column names would be a great help.<br /><br />I use
othertools with other databases that provide auto-completion anywhere in the query or update, even in joins on multiple
tables.For example, DB Artisan (for Sybase) offers a popup list of choices after a delay. If it is expecting a table,
thenthe list are the tables that "match". If it is expect a column, the list are the columns that "match"<br /><br
/>FWIW-- I tried SQL Assistant and rejected it for PgAdmin. The integration is clumsy (eg, wrt the connection) and, for
me,the gain (auto-completion on columns) is not worth the trouble that SQL Assistant creates.<br /><br /><br /><br
/><divclass="gmail_extra"><br /><br /><div class="gmail_quote">On Thu, Nov 29, 2012 at 6:50 AM, Dave Page <span
dir="ltr"><<ahref="mailto:dpage@pgadmin.org" target="_blank">dpage@pgadmin.org</a>></span> wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div
class="im">OnThu, Nov 29, 2012 at 5:53 PM, Michal Kozusznik<br /> <<a
href="mailto:kozusznik.michal@ifortuna.cz">kozusznik.michal@ifortuna.cz</a>>wrote:<br /> > On 29.11.2012 13:04,
DavePage wrote:<br /> >><br /> >> On Thu, Nov 29, 2012 at 3:02 PM, Kozusznik Michal<br /> >> <<a
href="mailto:kozusznik.michal@ifortuna.cz">kozusznik.michal@ifortuna.cz</a>>wrote:<br /> >>><br />
>>>that's why i'm not asking for developing hotkeys settings support, but to<br /> >>> add single
checkboxis setings to disable this feature at all. It should be<br /> >>> quick and easy.<br /> >><br />
>>But what is different between your request, and someone who has<br /> >> another app that uses F10 for
somethingother than Step Into in the<br /> >> debugger? We're not going to add the ability to disable a single
hot<br/> >> key on the request of one person I'm afraid. That leads to madness.<br /> ><br /> ><br /> >
Donot disable the single hotkey. Disable whole feature.<br /> > Man, I'm programmer too. Don't try to tell me it is
impossibleor hard to do<br /><br /></div>It's neither - it's probably a 20 minute job. But it's a random<br /> feature,
thatwill be inconsistent with the rest of the app, added at<br /> the request of one user in over 10 years. That is bad
design<br/> (inconsistency annoys users and causes confusion), and when repeated<br /> for every individual request
becomesan unmaintainable, messy<br /> codebase.<br /><div class="im"><br /> >> Auto-complete in pgAdmin uses the
samecode as psql does. That's<br /> >> regularly updated by the PostgreSQL team.<br /> ><br /> ><br /> >
Butunfortunately it's very weak comparable to other solutions. Aspecialy it<br /> > fails while working with joins.
butmakes impossible a lot of things like<br /> > add field names just after SELECT etc. I don't want to list all
issueshere.<br /> > There are better solutions - and this is the fact. That's why it should be<br /> > possible
todisable it in pgadmin.<br /> > Just try SQL Asistant to see how far behind is native auto-complete. Because<br />
>I have feeling you think psql based one is good enough.<br /><br /></div>I never use it myself. But out of
interest,how exactly to SQL<br /> Assistant give you any kind of usable auto complete for column names<br /> after
SELECTif you've got a database that's anything other than<br /> trivially sized? For example, the database I'm
currentlyworking in<br /> has nearly 4000 distinct columns in it, and that's relatively small.<br /><div class="im"><br
/>>>> Then you figure out that it doesn't make sense to block other apps which<br /> >>> do the job
better.<br/> >><br /> >> It doesn't block anything.<br /> >><br /> ><br /> > It does, actually
.It uses most popular hot-key combination making<br /> > impossible to use the same with SQL Assistant<br /><br
/></div>What,you mean Ctrl+Space is captured by pgAdmin, even if it doesn't<br /> have focus? It isn't here.<br /><div
class="imHOEnZb"><br /> --<br /> Dave Page<br /> Blog: <a href="http://pgsnake.blogspot.com"
target="_blank">http://pgsnake.blogspot.com</a><br/> Twitter: @pgsnake<br /><br /> EnterpriseDB UK: <a
href="http://www.enterprisedb.com"target="_blank">http://www.enterprisedb.com</a><br /> The Enterprise PostgreSQL
Company<br/><br /><br /></div><div class="HOEnZb"><div class="h5">--<br /> Sent via pgadmin-support mailing list (<a
href="mailto:pgadmin-support@postgresql.org">pgadmin-support@postgresql.org</a>)<br/> To make changes to your
subscription:<br/><a href="http://www.postgresql.org/mailpref/pgadmin-support"
target="_blank">http://www.postgresql.org/mailpref/pgadmin-support</a><br/></div></div></blockquote></div><br /></div>