That looks perfect. I'll look into it, and pass the link along to the pgAdmin
developers. I did bring up the suggestion to Dave Page who was kind enough
to take the auto complete request under consideration for the future when
they get to later stages of the product.
--
View this message in con
Oh perfect. Thanks for the heads up! I'll be sure to voice my request one way
or another during their design phase.
--
View this message in context:
http://postgresql.nabble.com/PSQL-pgAdmin-Column-Completion-tp5832573p5832603.html
Sent from the PostgreSQL - general mailing list archive at Nab
True - I placed this message in general, because all the history I could find
with the pgAdmin mailing lists suggests that they /really/ don't want to
break away from the psql tab completion code and run their own. Those
messages are a few years old, however - maybe things have changed.
I agree a
The majority of my query writing is done in pgAdmin, not psql. I do tend to
type out the from/where/join/whatever portion of the statement before
finishing the select portion of the statement (starting with a SELECT * and
replacing it once the rest of the query is in place). Fair enough, though --
ohibited. If you have received this communication in error, please
contact Club Speed, Inc. at (877) 751-3200.
On Wed, Dec 31, 2014 at 11:51 AM, Tom Lane-2 [via PostgreSQL] <
ml-node+s1045698n583257...@n5.nabble.com> wrote:
> dvlsg <[hidden email]
> <http:///user/SendEmail.jtp?type=n
I have been having issues with autocomplete in pgAdmin. After some searching,
I found it was my mistake and that pgAdmin doesn't actually support column
autocompletion in select statements. I found that pgAdmin uses the
autocomplete code directly from psql's tab-complete.c, which contains these
com
