aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2007-09-14 04:25:24 +0000
committerBruce Momjian <bruce@momjian.us>2007-09-14 04:25:24 +0000
commit17aae41afdd419a5921e75d3dd9fc29a8f18851d (patch)
treefd2b5ab686fc9271299958ccc6becc77184fa019 /src/backend/access/gist
parentc0f2b109bce3e6518ee1b78fb2bd90369e4781af (diff)
downloadpostgresql-17aae41afdd419a5921e75d3dd9fc29a8f18851d.tar.gz
postgresql-17aae41afdd419a5921e75d3dd9fc29a8f18851d.zip
Add tsearch tab completion support:
* adds a few missing words to some commands (like adding GIN as a valid index type or OWNED BY for ALTER SEQUENCE,...) * support for ALTER TABLE foo ENABLE/DISABLE REPLICA TRIGGER/RULE * autocomplete CREATE DATABASE foo TEMPLATE (mostly done to prevent conflicts with the TEMPLATE keyword for text search) * support for ALTER/CREATE/DROP TEXT SEARCH as well as COMMENT ON TEXT SEARCH and the corresponding psql backslash commands. This proved a little more difficult than expected due to the fact that words_after_create[] is used for two purposes - one is to provide a list of words that follow immediatly after CREATE (or DROP) and the other purpose is to use it for autocompleting anywhere in the statement if the word in that struct is found with a query. Since TEXT SEARCH CONFIGURATION|DICTIONARY|TEMPLATE|PARSER results in 3 words instead of one (as all the other words in that list are) I added a flag to the struct to tell create_command_generator() to skip that entry for autocompleting immediatly after CREATE which feels like a dirty hack (but that holds true for a lot of code in tab-complete.c). Stefan Kaltenbrunner
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions