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
On Wed, Dec 31, 2014, at 12:01 PM, dvlsg wrote:
> Yeah, I think that would be problematic. All other sql query
> applications I've used in the past with autocomplete seem to parse the
> entire query and find table references for autocompletion based on the
> whole query, whereas psql seems to typi
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
On 12/31/2014 03:12 PM, dvlsg wrote:
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 -
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
dvlsg writes:
> 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).
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 --
On 12/31/2014 01:55 PM, John R Pierce wrote:
On 12/31/2014 11:56 AM, Rob Sargent wrote:
I think I see the autocompleters lining up now:
just "my" schemas
we have single schemas with 100s of tables.
I'll type the from clause first
but, the sql command is SELECT field,field FROM tables
On 12/31/2014 11:56 AM, Rob Sargent wrote:
I think I see the autocompleters lining up now:
just "my" schemas
we have single schemas with 100s of tables.
I'll type the from clause first
but, the sql command is SELECT field,field FROM tables ... so how do
you type FROM before yo
Yeah, I think that would be problematic. All other sql query applications
I've used in the past with autocomplete seem to parse the entire query and
find table references for autocompletion based on the whole query, whereas
psql seems to typically base autocomplete off of the current cursor
locatio
On 12/31/2014 12:51 PM, Tom Lane wrote:
dvlsg writes:
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 dir
dvlsg writes:
> 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, w
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
13 matches
Mail list logo
