I've been doing all of my 'on the fly' SQL in vim or vi. On Windows, I use this in vim, and on AIX (where currently there is only vi installed, and I only access Informix databases), I use a different shortcut to send SQL to Informix's 'dbaccess'. For the vi version, I use the following two statements in my .exrc file (and they say perl is line noise :-) :

map #1 ma/^}/^M:?^{?,.t.^Mk:?^{?+1,.!dbvi^M'a
map #2 ma:/^{/;/^}/d^M'a
[download]

I have a shell script named 'dbvi' (which filters the input before sending it to dbaccess or elsewhere), and when the cursor is in any block delimited by braces, it sends the contents of the block to the shell script, and the results appear following the current block. E.g. Hitting F1 in the first block produces the next block:

{
select * from some_table
}
{
<results of query>
}
[download]

Hitting F2 in the current block deletes the following block. I did have to mess with terminfo to get the F-keys to work. In the vim version, I open new windows, so I don't have to deal with this block stuff...

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.