First of all, VoraX 2.8 is faster because it has a redesigned OS interface. This becomes obvious especially on Cygwin. Till now, there was an annoying delay immediately after a statement was finished executing. That was because another call was made in order to get connection information, which was further used to update the VoraX title. In VoraX 2.8 this is no longer true, the connection info is gathered in one step, as part of the statement execution itself.
Another useful feature is the monitoring capability of the results window. If you have a long running statement and you want to be notified when it's done then this is perfectly doable in VoraX 2.8. And because a picture worths one thousands words, below is a screen-shot showing this feature on my Ubuntu box:
Just put the following snippet into your .vimrc:
" Nice notification for my monitored long runinng queries function VoraxNotification() let cmd = "notify-send -i 'terminal' 'VoraX' 'Execution of your monitored statement on ". \ &titlestring . " has just finished.'" exe 'silent! !' . cmd endfunction let g:vorax_notify_command = "call VoraxNotification()"
On Windows I have no idea how to configure this but I guess there are some "cool" command line programs to display those annoying balloons in your tray.
And that's not all. Did you noticed the re-polished status line for the results window? Much better, isn't it?
As far as bug fixes are concerned I recommend you to upgrade because this version has a fix for a quite critical bug reported by Shaun Batterton. The bug description goes like this: if your statement has an "end" somewhere in between then a "/" will be appended. For example, if you execute something like:
alter tablespace muci_tbs add datafile size 100m autotextend on;
behind VoraX will rewrite (in a wrong way because of the bug) as:
alter tablespace muci_tbs add datafile size 100m autoextend on; /
I know it's stupid but because the statement has an "end" (in autoextend) we end up adding two datafiles which, of course, is not what we've meant. Thanks Shaun for this bug report.
There's also another bug fix in connection with virtualedit setting but that's not something to pay too much attention in this post.
Okey, that's all. You may find additional details about these new features within the VoraX updated documentation.