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. Currently Mysql, PostgreSQL, Ingres, Oracle, Sybase Adaptive Server Anywhere, Sybase Adaptive Server Enterprise, Microsoft SQL Server, DB2, RDB, SAP HANA and Interbase are supported. If you have a Perl enabled Vim, it also allows database connections via DBI and 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 20.00? New Features ------------ - Added new DBI/ODBC option DBI_max_column_width to restrict the width displayed in the DBI result window (Luke Mauldin). - Improved the pattern used to find the query under the cursor. Besides finding the command terminator, it will also look for the first blank line or the end of the file (Jason Quirk). - The dbext menu now uses the maps rather than calls to the commands. A new option will control this behaviour, g:dbext_map_or_cmd. - Changed the default SQLite binary to be sqlite3 instead of sqlite (Greg Kapfhammer). - Added a profile example for using the "sqsh" binary to connect to SQL Server instead of "osql" (Brian Iván Martínez). - The cmd_terminator displayed under Connection Options in the DBGetOption output was always blank. - Improved support for SAP HANA database, pulling objects from the system catalogue. Bug Fixes --------- - Controlling the DBI max rows (:DBSetOption DBI_max_rows=100) and DBI column separator did not work on a per buffer basis. - Undefined variable, s:dbext_prev_winnr, was reported when using DBI/ODBC connections through the sqlComplete plugin and completing objects which require an active database connection (i.e. Tables, Procedures, ...) which had failed to connect to the database. - dbext was not prompting for ? parameters in PHP files. This also affected all languages (Jérémie). - Changing a database's global cmd terminator was not necessarily picked up when using that database type (Jason Quirk). - ODBC or DBI could report an error about using length() instead of scalar() (Micah Duke). - Various errors on Linux with DBI (Micah Duke). - Using the console version of Vim displayed a number of "debug" messages during initialization. I am always open to suggestions, just email me. Dave -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
