On 16 July 2010 16:04, Greg Sabino Mullane <g...@turnstep.com> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > >> Someone highlighed on IRC that after the first WHERE clause, >> autocomplete no longer works. > ... >> SELECT * FROM tab_completion WHERE id = 2 AND s<tab><tab> > ... >> Is there any chance of improving this so it would work for more than 1 >> WHERE clause? I notice it also doesn't work for GROUP BY or HAVING at >> all, but seems to be fine for ORDER BY. > > No: there is only a small number of words that we go back through, > so the above will not work as we cannot get back to the name of the table > from the right side of the AND. The way to fix that is to redesign our > tab-completion system such that it knows about a greater number of words, > perhaps even the complete statement. >
Yay for complete overhauls! Okay, fair enough. Bit unintuitive behaviour though. >> SELECT * FROM tab_completion WHERE id = 2 AND b<tab> >> >> Since there is no column beginning with "b", it might be an idea to >> get it to match "bark bark" instead. It might help alleviate what may >> be a gotcha for some. > > This one is more doable, assuming we are really talking about: > > SELECT * FROM tab_completion WHERE b<tab> > > Keep in mind it will show up in a list if you do the following: > > SELECT * FROM tab_completion WHERE <tab> > > Doesn't it do that already? Thom -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
