Hello Sherman, I see no reason to use web-page instead of plain old console with the interactive iSQL client.
The web-page is for urgent manipulations when the administrator is far away and can not get any better access to the system, because, say, his mobile has no terminal app but that's all the admin brought to the weekend beach party. You have the box in your whole possession, so you can use any editors and terminals of your choice. You can simply edit the .SQL file, reload it from console app, test the effect and continue to edit. The isql is shipped with Virtuoso, both reside in same directory after installation. The system can have many tools named isql, in different directories, they may come from different database vendors. For use with Virtuoso, the use of Virtuoso's own isql client is obviously recommended. Best Regards, Ivan Mikhailov OpenLink Software http://virtuoso.openlinksw.com On Tue, 2011-08-30 at 11:47 -0500, Sherman Monroe wrote: > Hi Ivan, > > > I'm trying to pin down the steps: > > > 1. open the interactive SQL interface > 2. enter one or more SQL files, delimited by semi-colon > 3. press the 'execute' button > > > Is this correct? Also, how do I specify that I wish to replace an old > SQL procedure with a new one? Is there an "edit" function in the iSQL > interface? > > > Thanks, > -sherman > > On Tue, Aug 30, 2011 at 1:01 AM, Ivan Mikhailov > <[email protected]> wrote: > Hello Sherman, > > > Is there any document that cover the development/testing > phase of the > > VAD lifecycle? I can't imagine that I would need to redeploy > each time > > I wanted to modify and test new SQL. > > > There's little need in any special techniques for VAD, because > 99.99% of > the application code resides in plain old .SQL files that can > be edited > by any appropriate editor and loaded via ISQL. The only > requirement for > them is to put ending ';' of statements at separate lines, so > the VAD > routines will cut the file by semicolon-only lines. As soon as > all .SQL > files are ready and tested on fresh empty database, writing > the .vad > file itself is quite simple (and patching some existing one is > even > simpler) > > Best Regards, > > Ivan Mikhailov > OpenLink Software > http://virtuoso.openlinksw.com Thanks, > -sherman
