What is it?
-----------
dbext.vim : Provides database access to most databases.
http://www.vim.org/scripts/script.php?script_id=356
This plugin contains functions/mappings/commands to enable Vim to
access several databases.
This plugin contains functions/mappings/commands to enable Vim to
access several databases.
List of currently supported databases:
DB2
Firebird
Ingres
Interbase
Microsoft SQL Server
MySQL
PostgreSQL
Oracle
Oracle Rdb on an Open VMS Node
SQLite
Sybase Adaptive Server Anywhere
Sybase UltraLite
Sybase Adaptive Server Enterprise
When using a Perl enabled Vim ( :echo has('perl') ):
DBI
ODBC
It abstracts database access, so the same Vim commands will produce
the same output regardless of the database you use.
What is new in 11.00?
New Features
------------
- When autoclose is enabled, a message is displayed indicating autoclose is
enabled. This message will now also include the number of rows affected
by the last statement (if applicable). This is available for all
database interfaces which can provide this information. Vim scripts or
mappings have access to this value by referencing the g:dbext_rows_affected
variable (Philippe Moravie).
- The Select, Update, Delete, Alter and Drop commands will now complete
table names.
- Revamped the saved variables (see |dbext-tutorial-variables|). dbext
checks your queries and will prompt for variables (see |dbext-prompting|).
dbext uses regular expressions to determine which variables should be
prompted. To see how you can easily extend the regular expressions follow
the tutorial. This replaces the previous method which was too limiting.
The new technique uses Vim's standard regular expressions. This introduces
the variable_def_regex dbext option and deprecates the variable_def dbext
option.
- With the introduction of saved variables, you are now prompted during
SQL execution to determine whether the previously saved variables
should be substituted.
Bug Fixes
---------
- If you re-sourced plugin/dbext.vim you would receive the following error:
E227: mapping already exists for <Leader>sas
- Errors were reported about undefined variable, dbext_sqlvar_temp_mv, if
executing a SQL statement directly from a filetype which was not SQL
(i.e. PHP).
- If saved variables were in use, it was possible for dbext to used the
replaced variables without the user knowing. For example stored
procedures could be created with the replaced strings instead of the
variables.
If you have comments or suggestions, please free to contact me.
Enjoy.
David Fishburn
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
