Version 6.00

Posted by David Fishburn

New Features
------------
- dbext now supports table and column names which can contain spaces (Antony Scriven).  There is a corresponding change to sqlcomplete.vim to support this.
- Added an autoclose option.  If you execute SQL which does not return a result set you can choose to have the dbext results window automatically close (unless of course there was an error).  See the autoclose option for more details.
- Added the map shortcuts to each of menu items under the dbext menu so that users can learn them more easily (Alexander Langer).
- Using the menu_mode option you can control if and where the dbext menu is created (Marty Grenfell).  See the menu_mode option for more details.
- For MySQL, added -t as part of the default command line parameters setting.  This will properly format the data into tabs or spaces to make it more readable (Luke Cordingley).
- A message is displayed indicating the time a SQL command began executing.  The result window also contains the time the SQL finished executing.
- DBI or ODBC can now fetch BLOB columns from the database.  By default these are truncated at 500 characters, but that can be changed by issuing: DBSetOption driver_parms=LongReadLen=4096

Bug Fixes
---------
- If a database column had an emdedded double quote this would be displayed as \" in the dbext result window (Jean-Christophe Clavier).
- When loading the plugin, it will now check to ensure the map does not already exist before attempting to create it.  This will prevent errors when mappings clash (Antony Scriven).
- If you prompt for connection parameters using the DBI or ODBC types we need to disconnect any existing connections or the existing connection will continue to be used.
- In some cases when using DBI or ODBC an error was not reported and only a blank result set was returned.  Now the database error is reported back to the user.
- Data retrieved via DBI or ODBC which contained a backslash were not escaped properly and could disappear.

Author: bagyi0