You are welcome! :) BTW, I want to make a feature request. Is it possible to keep all sql query outputs(last one on top) in the result buffer? maybe an option or a command or whatever. I find I often first view the table's definition, then make some query on the table, then want to go back to see the definition again.
Thanks and look forward to the new version :) BR Vincent On Feb 6, 10:16 pm, [email protected] wrote: > Thanks Vincent, I have already fixed it but was making other changes and am > testing before uploading. > > Thanks for the note. > Dave > > Sent from my BlackBerry device on the Rogers Wireless Network > > -----Original Message----- > From: vincent <[email protected]> > > Date: Fri, 6 Feb 2009 06:07:28 > To: vim_use<[email protected]> > Subject: Re: ANN:dbext9.00 > > Hi, > > After I encounter one issue with this new version:dbextmodeline stop > working. > > I just made a dirty hack to make things work. I don't read the related > codes thoroughly, maybe my solution is wrong, but till now, it works > well for me. > > the fix just adds following lines under line 1070 in file autoload/dbext.vim: > > if a:use_defaults == 0 > " for this case, no need to run following codes, just return > " sucess to caller since all params have been reset > let retval = 1 > return retval > endif > > BR > Vincent > > On Jan 10, 12:11 pm, "David Fishburn" <[email protected]> wrote: > > 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 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 9.00? > > > New Features > > ------------ > > - Added the ability to set and store SQL variables for each buffer. > > This will reduce prompting for statements which are often re-used. > > Added support for listing and deleting SQL variables. Initial > > prototype by Garrison Yu. > > - Added option, g:dbext_default_variable_remember, to control whether > > SQL variables should be stored when prompted. > > - Improved the parsing of SQL statements to account for procedural > > language. If a IN, OUT, INOUT or DECLARE statement is found prior to > > the use of the variable, it is stored for later use. When the > > variable is encountered, if the declaration was found we skip > > prompting for it's value. This should reduce the number of prompts > > you receive when executing SQL (i.e. Functions, Procedures, Events, > > Packages and so on depending on the naming convention you use for your > > variables. > > - Updated the tutorial and added more links to different sections see > > |dbext-tutorial-variable| > > - Added VB filetype support (Garrison Yu). > > - Added escaping to allow specifying an new Oracle URL syntax for > > server connection parameters (Anton Sharonov). > > - Renamed DBCloseResults, DBOpenResults, DBRefreshResult, > > DBToggleResultsResize to DBResultsClose, DBResultsOpen, > > DBResultsRefresh, DBResultsToggleResize to be more consistent. > > > Bug Fixes > > --------- > > - You are often repeatedly prompted for connection information. This > > change reduces the number and allows you to cancel out of the prompt > > dialogs. > > - Added an unconditional quit command to exit out of Oracle's SQLPlus > > (Anton Sharonov). > > > Enjoy, and remember feedback always welcome. > > Dave --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
