1
*sql.txt* For Vim version 7.1. Last change: Wed Apr 26 2006 3:05:33 PM
5
This is a filetype plugin to work with SQL files.
7
The Structured Query Language (SQL) is a standard which specifies statements
8
that allow a user to interact with a relational database. Vim includes
9
features for navigation, indentation and syntax highlighting.
11
1. Navigation |sql-navigation|
12
1.1 Matchit |sql-matchit|
13
1.2 Text Object Motions |sql-object-motions|
14
1.3 Predefined Object Motions |sql-predefined-objects|
15
1.4 Macros |sql-macros|
16
2. SQL Dialects |sql-dialects|
17
2.1 SQLSetType |SQLSetType|
18
2.2 SQL Dialect Default |sql-type-default|
19
3. Adding new SQL Dialects |sql-adding-dialects|
20
4. OMNI SQL Completion |sql-completion|
21
4.1 Static mode |sql-completion-static|
22
4.2 Dynamic mode |sql-completion-dynamic|
23
4.3 Tutorial |sql-completion-tutorial|
24
4.3.1 Complete Tables |sql-completion-tables|
25
4.3.2 Complete Columns |sql-completion-columns|
26
4.3.3 Complete Procedures |sql-completion-procedures|
27
4.3.4 Complete Views |sql-completion-views|
28
4.4 Completion Customization |sql-completion-customization|
29
4.5 SQL Maps |sql-completion-maps|
30
4.6 Using with other filetypes |sql-completion-filetypes|
32
==============================================================================
33
1. Navigation *sql-navigation*
35
The SQL ftplugin provides a number of options to assist with file
39
1.1 Matchit *sql-matchit*
41
The matchit plugin (http://www.vim.org/scripts/script.php?script_id=39)
42
provides many additional features and can be customized for different
43
languages. The matchit plugin is configured by defining a local
44
buffer variable, b:match_words. Pressing the % key while on various
45
keywords will move the cursor to its match. For example, if the cursor
46
is on an "if", pressing % will cycle between the "else", "elseif" and
49
The following keywords are supported: >
55
[while condition] loop
83
create[ or replace] procedure|function|event
87
1.2 Text Object Motions *sql-object-motions*
88
-----------------------
89
Vim has a number of predefined keys for working with text |object-motions|.
90
This filetype plugin attempts to translate these keys to maps which make sense
93
The following |Normal| mode and |Visual| mode maps exist (when you edit a SQL
95
]] move forward to the next 'begin'
96
[[ move backwards to the previous 'begin'
97
][ move forward to the next 'end'
98
[] move backwards to the previous 'end'
101
1.3 Predefined Object Motions *sql-predefined-objects*
102
-----------------------------
103
Most relational databases support various standard features, tables, indices,
104
triggers and stored procedures. Each vendor also has a variety of proprietary
105
objects. The next set of maps have been created to help move between these
106
objects. Depends on which database vendor you are using, the list of objects
107
must be configurable. The filetype plugin attempts to define many of the
108
standard objects, plus many additional ones. In order to make this as
109
flexible as possible, you can override the list of objects from within your
110
|vimrc| with the following: >
111
let g:ftplugin_sql_objects = 'function,procedure,event,table,trigger' .
112
\ ',schema,service,publication,database,datatype,domain' .
113
\ ',index,subscription,synchronization,view,variable'
115
The following |Normal| mode and |Visual| mode maps have been created which use
117
]} move forward to the next 'create <object name>'
118
[{ move backward to the previous 'create <object name>'
120
Repeatedly pressing ]} will cycle through each of these create statements: >
130
create index i1 on t1 (c1);
132
The default setting for g:ftplugin_sql_objects is: >
133
let g:ftplugin_sql_objects = 'function,procedure,event,' .
134
\ '\\(existing\\\\|global\\s\\+temporary\\s\\+\\)\\\{,1}' .
136
\ ',schema,service,publication,database,datatype,domain' .
137
\ ',index,subscription,synchronization,view,variable'
139
The above will also handle these cases: >
143
create existing table t2 (
146
create global temporary table t3 (
150
By default, the ftplugin only searches for CREATE statements. You can also
151
override this via your |vimrc| with the following: >
152
let g:ftplugin_sql_statements = 'create,alter'
154
The filetype plugin defines three types of comments: >
161
The following |Normal| mode and |Visual| mode maps have been created to work
163
]" move forward to the beginning of a comment
164
[" move forward to the end of a comment
168
1.4 Macros *sql-macros*
170
Vim's feature to find macro definitions, |'define'|, is supported using this
171
regular expression: >
172
\c\<\(VARIABLE\|DECLARE\|IN\|OUT\|INOUT\)\>
174
This addresses the following code: >
175
CREATE VARIABLE myVar1 INTEGER;
177
CREATE PROCEDURE sp_test(
180
INOUT myVar4 NUMERIC(20,0)
183
DECLARE myVar5 INTEGER;
186
INTO myVar2, myVar3, myVar4
191
Place your cursor on "myVar1" on this line: >
195
Press any of the following keys: >
201
==============================================================================
202
2. SQL Dialects *sql-dialects* *sql-types*
203
*sybase* *TSQL* *Transact-SQL*
205
*oracle* *plsql* *sqlj*
207
*mysql* *postgres* *psql*
210
All relational databases support SQL. There is a portion of SQL that is
211
portable across vendors (ex. CREATE TABLE, CREATE INDEX), but there is a
212
great deal of vendor specific extensions to SQL. Oracle supports the
213
"CREATE OR REPLACE" syntax, column defaults specified in the CREATE TABLE
214
statement and the procedural language (for stored procedures and triggers).
216
The default Vim distribution ships with syntax highlighting based on Oracle's
217
PL/SQL. The default SQL indent script works for Oracle and SQL Anywhere.
218
The default filetype plugin works for all vendors and should remain vendor
219
neutral, but extendable.
221
Vim currently has support for a variety of different vendors, currently this
222
is via syntax scripts. Unfortunately, to flip between different syntax rules
223
you must either create:
226
3. Manual steps / commands
228
The majority of people work with only one vendor's database product, it would
229
be nice to specify a default in your |vimrc|.
232
2.1 SQLSetType *sqlsettype* *SQLSetType*
234
For the people that work with many different databases, it would be nice to be
235
able to flip between the various vendors rules (indent, syntax) on a per
236
buffer basis, at any time. The ftplugin/sql.vim file defines this function: >
239
Executing this function without any parameters will set the indent and syntax
240
scripts back to their defaults, see |sql-type-default|. If you have turned
241
off Vi's compatibility mode, |'compatible'|, you can use the <Tab> key to
242
complete the optional parameter.
244
After typing the function name and a space, you can use the completion to
245
supply a parameter. The function takes the name of the Vim script you want to
246
source. Using the |cmdline-completion| feature, the SQLSetType function will
247
search the |'runtimepath'| for all Vim scripts with a name containing 'sql'.
248
This takes the guess work out of the spelling of the names. The following are
251
:SQLSetType sqloracle
252
:SQLSetType sqlanywhere
253
:SQLSetType sqlinformix
256
The easiest approach is to the use <Tab> character which will first complete
257
the command name (SQLSetType), after a space and another <Tab>, display a list
258
of available Vim script names: >
259
:SQL<Tab><space><Tab>
262
2.2 SQL Dialect Default *sql-type-default*
263
-----------------------
264
As mentioned earlier, the default syntax rules for Vim is based on Oracle
265
(PL/SQL). You can override this default by placing one of the following in
267
let g:sql_type_default = 'sqlanywhere'
268
let g:sql_type_default = 'sqlinformix'
269
let g:sql_type_default = 'mysql'
271
If you added the following to your |vimrc|: >
272
let g:sql_type_default = 'sqlinformix'
274
The next time edit a SQL file the following scripts will be automatically
277
syntax/sqlinformix.vim
280
Notice indent/sqlinformix.sql was not loaded. There is no indent file
281
for Informix, Vim loads the default files if the specified files does not
285
==============================================================================
286
3. Adding new SQL Dialects *sql-adding-dialects*
288
If you begin working with a SQL dialect which does not have any customizations
289
available with the default Vim distribution you can check http://www.vim.org
290
to see if any customization currently exist. If not, you can begin by cloning
291
an existing script. Read |filetype-plugins| for more details.
293
To help identify these scripts, try to create the files with a "sql" prefix.
294
If you decide you wish to create customizations for the SQLite database, you
295
can create any of the following: >
297
~/.vim/syntax/sqlite.vim
298
~/.vim/indent/sqlite.vim
300
$VIM/vimfiles/syntax/sqlite.vim
301
$VIM/vimfiles/indent/sqlite.vim
303
No changes are necessary to the SQLSetType function. It will automatically
304
pickup the new SQL files and load them when you issue the SQLSetType command.
307
==============================================================================
308
4. OMNI SQL Completion *sql-completion*
309
*omni-sql-completion*
311
Vim 7 includes a code completion interface and functions which allows plugin
312
developers to build in code completion for any language. Vim 7 includes
313
code completion for the SQL language.
315
There are two modes to the SQL completion plugin, static and dynamic. The
316
static mode populates the popups with the data generated from current syntax
317
highlight rules. The dynamic mode populates the popups with data retrieved
318
directly from a database. This includes, table lists, column lists,
319
procedures names and more.
321
4.1 Static Mode *sql-completion-static*
323
The static popups created contain items defined by the active syntax rules
324
while editing a file with a filetype of SQL. The plugin defines (by default)
325
various maps to help the user refine the list of items to be displayed.
326
The defaults static maps are: >
327
imap <buffer> <C-C>a <C-\><C-O>:call sqlcomplete#Map('syntax')<CR><C-X><C-O>
328
imap <buffer> <C-C>k <C-\><C-O>:call sqlcomplete#Map('sqlKeyword')<CR><C-X><C-O>
329
imap <buffer> <C-C>f <C-\><C-O>:call sqlcomplete#Map('sqlFunction')<CR><C-X><C-O>
330
imap <buffer> <C-C>o <C-\><C-O>:call sqlcomplete#Map('sqlOption')<CR><C-X><C-O>
331
imap <buffer> <C-C>T <C-\><C-O>:call sqlcomplete#Map('sqlType')<CR><C-X><C-O>
332
imap <buffer> <C-C>s <C-\><C-O>:call sqlcomplete#Map('sqlStatement')<CR><C-X><C-O>
334
The static maps (which are based on the syntax highlight groups) follow this
336
imap <buffer> <C-C>k <C-\><C-O>:call sqlcomplete#Map('sqlKeyword')<CR><C-X><C-O>
338
This command breaks down as: >
339
imap - Create an insert map
340
<buffer> - Only for this buffer
341
<C-C>k - Your choice of key map
342
<C-\><C-O> - Execute one command, return to Insert mode
343
:call sqlcomplete#Map( - Allows the SQL completion plugin to perform some
344
housekeeping functions to allow it to be used in
345
conjunction with other completion plugins.
346
Indicate which item you want the SQL completion
348
In this case we are asking the plugin to display
349
items from the syntax highlight group
351
You can view a list of highlight group names to
352
choose from by executing the
354
command while editing a SQL file.
355
'sqlKeyword' - Display the items for the sqlKeyword highlight
357
)<CR> - Execute the :let command
358
<C-X><C-O> - Trigger the standard omni completion key stroke.
359
Passing in 'sqlKeyword' instructs the SQL
360
completion plugin to populate the popup with
361
items from the sqlKeyword highlight group. The
362
plugin will also cache this result until Vim is
363
restarted. The syntax list is retrieved using
364
the syntaxcomplete plugin.
366
Using the 'syntax' keyword is a special case. This instructs the
367
syntaxcomplete plugin to retrieve all syntax items. So this will effectively
368
work for any of Vim's SQL syntax files. At the time of writing this includes
369
10 different syntax files for the different dialects of SQL (see section 3
370
above, |sql-dialects|).
372
Here are some examples of the entries which are pulled from the syntax files: >
374
- Contains the contents of all syntax highlight groups
376
- Select, Insert, Update, Delete, Create, Alter, ...
378
- Min, Max, Trim, Round, Date, ...
380
- Index, Database, Having, Group, With
382
- Isolation_level, On_error, Qualify_owners, Fire_triggers, ...
384
- Integer, Char, Varchar, Date, DateTime, Timestamp, ...
387
4.2 Dynamic Mode *sql-completion-dynamic*
389
Dynamic mode populates the popups with data directly from a database. In
390
order for the dynamic feature to be enabled you must have the dbext.vim
391
plugin installed, (http://vim.sourceforge.net/script.php?script_id=356).
393
Dynamic mode is used by several features of the SQL completion plugin.
394
After installing the dbext plugin see the dbext-tutorial for additional
395
configuration and usage. The dbext plugin allows the SQL completion plugin
396
to display a list of tables, procedures, views and columns. >
398
- All tables for all schema owners
400
- All stored procedures for all schema owners
402
- All stored procedures for all schema owners
404
- For the selected table, the columns that are part of the table
406
To enable the popup, while in INSERT mode, use the following key combinations
407
for each group (where <C-C> means hold the CTRL key down while pressing
410
- <C-X><C-O> (the default map assumes tables)
411
Stored Procedure List - <C-C>p
415
Windows platform only - When viewing a popup window displaying the list
416
of tables, you can press <C-Right>, this will
417
replace the table currently highlighted with
418
the column list for that table.
419
- When viewing a popup window displaying the list
420
of columns, you can press <C-Left>, this will
421
replace the column list with the list of tables.
422
- This allows you to quickly drill down into a
423
table to view it's columns and back again.
425
The SQL completion plugin caches various lists that are displayed in
426
the popup window. This makes the re-displaying of these lists very
427
fast. If new tables or columns are added to the database it may become
428
necessary to clear the plugins cache. The default map for this is: >
429
imap <buffer> <C-C>R <C-\><C-O>:call sqlcomplete#Map('ResetCache')<CR><C-X><C-O>
432
4.3 SQL Tutorial *sql-completion-tutorial*
435
This tutorial is designed to take you through the common features of the SQL
436
completion plugin so that: >
437
a) You gain familiarity with the plugin
438
b) You are introduced to some of the more common features
439
c) Show how to customize it to your preferences
440
d) Demonstrate "Best of Use" of the plugin (easiest way to configure).
442
First, create a new buffer: >
448
To take you through the various lists, simply enter insert mode, hit:
449
<C-C>s (show SQL statements)
450
At this point, you can page down through the list until you find "select".
451
If you are familiar with the item you are looking for, for example you know
452
the statement begins with the letter "s". You can type ahead (without the
453
quotes) "se" then press:
455
Assuming "select" is highlighted in the popup list press <Enter> to choose
457
* fr<C-C>a (show all syntax items)
458
choose "from" from the popup list.
460
When writing stored procedures using the "type" list is useful. It contains
461
a list of all the database supported types. This may or may not be true
462
depending on the syntax file you are using. The SQL Anywhere syntax file
463
(sqlanywhere.vim) has support for this: >
465
DECLARE customer_id <C-C>T <-- Choose a type from the list
470
To take advantage of the dynamic features you must first install the
471
dbext.vim plugin (http://vim.sourceforge.net/script.php?script_id=356). It
472
also comes with a tutorial. From the SQL completion plugin's perspective,
473
the main feature dbext provides is a connection to a database. dbext
474
connection profiles are the most efficient mechanism to define connection
475
information. Once connections have been setup, the SQL completion plugin
476
uses the features of dbext in the background to populate the popups.
478
What follows assumes dbext.vim has been correctly configured, a simple test
479
is to run the command, :DBListTable. If a list of tables is shown, you know
480
dbext.vim is working as expected. If not, please consult the dbext.txt
483
Assuming you have followed the dbext-tutorial you can press <C-C>t to
484
display a list of tables. There is a delay while dbext is creating the table
485
list. After the list is displayed press <C-W>. This will remove both the
486
popup window and the table name already chosen when the list became active. >
488
4.3.1 Table Completion: *sql-completion-tables*
490
Press <C-C>t to display a list of tables from within the database you
491
have connected via the dbext plugin.
492
NOTE: All of the SQL completion popups support typing a prefix before pressing
493
the key map. This will limit the contents of the popup window to just items
494
beginning with those characters. >
496
4.3.2 Column Completion: *sql-completion-columns*
498
The SQL completion plugin can also display a list of columns for particular
499
tables. The column completion is trigger via <C-C>c.
501
NOTE: The following example uses <C-Right> to trigger a column list while
502
the popup window is active. This map is only available on the Windows
503
platforms since *nix does not recognize CTRL and the right arrow held down
504
together. If you wish to enable this functionality on a *nix platform choose
505
a key and create one of these mappings (see |sql-completion-maps| for further
506
details on where to create this imap): >
507
imap <buffer> <your_keystroke> <C-R>=sqlcomplete#DrillIntoTable()<CR>
508
imap <buffer> <your_keystroke> <C-Y><C-\><C-O>:call sqlcomplete#Map('column')<CR><C-X><C-O>
510
Example of using column completion:
511
- Press <C-C>t again to display the list of tables.
512
- When the list is displayed in the completion window, press <C-Right>,
513
this will replace the list of tables, with a list of columns for the
514
table highlighted (after the same short delay).
515
- If you press <C-Left>, this will again replace the column list with the
516
list of tables. This allows you to drill into tables and column lists
518
- Press <C-Right> again while the same table is highlighted. You will
519
notice there is no delay since the column list has been cached. If you
520
change the schema of a cached table you can press <C-C>R, which
521
clears the SQL completion cache.
522
- NOTE: <C-Right> and <C-Left> have been designed to work while the
523
completion window is active. If the completion popup window is
524
not active, a normal <C-Right> or <C-Left> will be executed.
526
Lets look how we can build a SQL statement dynamically. A select statement
527
requires a list of columns. There are two ways to build a column list using
528
the SQL completion plugin. >
529
One column at a time:
530
< 1. After typing SELECT press <C-C>t to display a list of tables.
531
2. Choose a table from the list.
532
3. Press <C-Right> to display a list of columns.
533
4. Choose the column from the list and press enter.
534
5. Enter a "," and press <C-C>c. Generating a column list
535
generally requires having the cursor on a table name. The plugin
536
uses this name to determine what table to retrieve the column list.
537
In this step, since we are pressing <C-C>c without the cursor
538
on a table name the column list displayed will be for the previous
539
table. Choose a different column and move on.
540
6. Repeat step 5 as often as necessary. >
541
All columns for a table:
542
< 1. After typing SELECT press <C-C>t to display a list of tables.
543
2. Highlight the table you need the column list for.
544
3. Press <Enter> to choose the table from the list.
545
4. Press <C-C>l to request a comma separated list of all columns
547
5. Based on the table name chosen in step 3, the plugin attempts to
548
decide on a reasonable table alias. You are then prompted to
549
either accept of change the alias. Press OK.
550
6. The table name is replaced with the column list of the table is
551
replaced with the comma separate list of columns with the alias
552
prepended to each of the columns.
553
7. Step 3 and 4 can be replaced by pressing <C-C>L, which has
554
a <C-Y> embedded in the map to choose the currently highlighted
557
There is a special provision when writing select statements. Consider the
558
following statement: >
567
In INSERT mode after typing the final "c." which is an alias for the
568
"customer" table, you can press either <C-C>c or <C-X><C-O>. This will
569
popup a list of columns for the customer table. It does this by looking back
570
to the beginning of the select statement and finding a list of the tables
571
specified in the FROM clause. In this case it notes that in the string
572
"customer c", "c" is an alias for the customer table. The optional "AS"
573
keyword is also supported, "customer AS c". >
576
4.3.3 Procedure Completion: *sql-completion-procedures*
578
Similar to the table list, <C-C>p, will display a list of stored
579
procedures stored within the database. >
581
4.3.4 View Completion: *sql-completion-views*
583
Similar to the table list, <C-C>v, will display a list of views in the
587
4.4 Completion Customization *sql-completion-customization*
588
----------------------------
590
The SQL completion plugin can be customized through various options set in
592
omni_sql_no_default_maps
593
< - Default: This variable is not defined
594
- If this variable is defined, no maps are created for OMNI
595
completion. See |sql-completion-maps| for further discussion.
597
omni_sql_use_tbl_alias
599
- This setting is only used when generating a comma separated
600
column list. By default the map is <C-C>l. When generating
601
a column list, an alias can be prepended to the beginning of each
602
column, for example: e.emp_id, e.emp_name. This option has three
604
n - do not use an alias
605
d - use the default (calculated) alias
606
a - ask to confirm the alias name
608
An alias is determined following a few rules:
609
1. If the table name has an '_', then use it as a separator: >
610
MY_TABLE_NAME --> MTN
611
my_table_name --> mtn
612
My_table_NAME --> MtN
613
< 2. If the table name does NOT contain an '_', but DOES use
614
mixed case then the case is used as a separator: >
616
< 3. If the table name does NOT contain an '_', and does NOT
617
use mixed case then the first letter of the table is used: >
622
< - Default: Current setting for|ignorecase|
623
- Valid settings are 0 or 1.
624
- When entering a few letters before initiating completion, the list
625
will be filtered to display only the entries which begin with the
626
list of characters. When this option is set to 0, the list will be
627
filtered using case sensitivity. >
629
omni_sql_include_owner
630
< - Default: 0, unless dbext.vim 3.00 has been installed
631
- Valid settings are 0 or 1.
632
- When completing tables, procedure or views and using dbext.vim 3.00
633
or higher the list of objects will also include the owner name.
634
When completing these objects and omni_sql_include_owner is enabled
635
the owner name will be replaced. >
637
omni_sql_precache_syntax_groups
639
['syntax','sqlKeyword','sqlFunction','sqlOption','sqlType','sqlStatement']
640
- sqlcomplete can be used in conjunction with other completion
641
plugins. This is outlined at |sql-completion-filetypes|. When the
642
filetype is changed temporarily to SQL, the sqlcompletion plugin
643
will cache the syntax groups listed in the List specified in this
647
4.5 SQL Maps *sql-completion-maps*
650
The default SQL maps have been described in other sections of this document in
651
greater detail. Here is a list of the maps with a brief description of each.
655
These are maps which use populate the completion list using Vim's syntax
656
highlighting rules. >
658
< - Displays all SQL syntax items. >
660
< - Displays all SQL syntax items defined as 'sqlKeyword'. >
662
< - Displays all SQL syntax items defined as 'sqlFunction. >
664
< - Displays all SQL syntax items defined as 'sqlOption'. >
666
< - Displays all SQL syntax items defined as 'sqlType'. >
668
< - Displays all SQL syntax items defined as 'sqlStatement'. >
672
These are maps which use populate the completion list using the dbext.vim
675
< - Displays a list of tables. >
677
< - Displays a list of procedures. >
679
< - Displays a list of views. >
681
< - Displays a list of columns for a specific table. >
683
< - Displays a comma separated list of columns for a specific table. >
685
< - Displays a comma separated list of columns for a specific table.
686
This should only be used when the completion window is active. >
688
< - Displays a list of columns for the table currently highlighted in
689
the completion window. <C-Right> is not recognized on most Unix
690
systems, so this maps is only created on the Windows platform.
691
If you would like the same feature on Unix, choose a different key
692
and make the same map in your vimrc. >
694
< - Displays the list of tables.
695
<C-Left> is not recognized on most Unix systems, so this maps is
696
only created on the Windows platform. If you would like the same
697
feature on Unix, choose a different key and make the same map in
700
< - This maps removes all cached items and forces the SQL completion
701
to regenerate the list of items.
705
You can create as many additional key maps as you like. Generally, the maps
706
will be specifying different syntax highlight groups.
708
If you do not wish the default maps created or the key choices do not work on
709
your platform (often a case on *nix) you define the following variable in
711
let g:omni_sql_no_default_maps = 1
713
Do no edit ftplugin/sql.vim directly! If you change this file your changes
714
will be over written on future updates. Vim has a special directory structure
715
which allows you to make customizations without changing the files that are
716
included with the Vim distribution. If you wish to customize the maps
717
create an after/ftplugin/sql.vim (see |after-directory|) and place the same
718
maps from the ftplugin/sql.vim in it using your own key strokes. <C-C> was
719
chosen since it will work on both Windows and *nix platforms. On the windows
720
platform you can also use <C-Space> or ALT keys.
723
4.6 Using with other filetypes *sql-completion-filetypes*
724
------------------------------
726
Many times SQL can be used with different filetypes. For example Perl, Java,
727
PHP, Javascript can all interact with a database. Often you need both the SQL
728
completion as well as the completion capabilities for the current language you
731
This can be enabled easily with the following steps (assuming a Perl file): >
738
Begins by editing a Perl file. Vim automatically sets the filetype to
739
"perl". By default, Vim runs the appropriate filetype file
740
ftplugin/perl.vim. If you are using the syntax completion plugin by following
741
the directions at |ft-syntax-omni| then the |'omnifunc'| option has been set to
742
"syntax#Complete". Pressing <C-X><C-O> will display the omni popup containing
743
the syntax items for Perl.
747
Manually setting the filetype to 'sql' will also fire the appropriate filetype
748
files ftplugin/sql.vim. This file will define a number of buffer specific
749
maps for SQL completion, see |sql-completion-maps|. Now these maps have
750
been created and the SQL completion plugin has been initialized. All SQL
751
syntax items have been cached in preparation. The SQL filetype script detects
752
we are attempting to use two different completion plugins. Since the SQL maps
753
begin with <C-C>, the maps will toggle the |'omnifunc'| when in use. So you
754
can use <C-X><C-O> to continue using the completion for Perl (using the syntax
755
completion plugin) and <C-C> to use the SQL completion features.
759
Setting the filetype back to Perl sets all the usual "perl" related items back
763
vim:tw=78:ts=8:ft=help:norl:
added
removed
runtime/doc/sql.txt
