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
