SqlDbx
You are not logged in.
Pages: 1
I have written various automated scripts and have placed them into speed typing. Some output needs to be in Grid for exporting to Excel, some need to be in Text for copying into the run area and executing.
Getting to my point, another handy enhancement would be to have a programmable way of setting the Result method before the script runs.
As an example, suppose XSET was a SqlDbx-specific command.
- - - - -
XSET result = 'G'
SELECT....
- - - - -
This would be a great enhancement for various other SqlDbx options too, like a programmable toggle for "Include Result Text Only" set to Tor F. (XSET textonly = 'T')
In my thinking, anytime XSET (or whatever syntax you decide to use) is placed into a script, sqldbx would understand it and run it, without any errors from databases. Perhaps these commands would need to be at the top and separated somehow. You get the idea.
Jason Lipman
Functionality to do something like this already exists in SqlDbx but currently disabled.
So far we did not find good use for it. Your idea sound interesting.
Offline
An extension to this idea would also allow the result set to be written to a file with a possibility of selecting how it is to be written e.g. csv, insert statements. This would require these statements to be embedded anywhere in the script to allow for multiple result sets. Possible suggestion to identify SQLDbx specific command would be to prefix it with something e.g. --XSET or #XSET
Offline
We enabled script commands functionality in a latest test release
See help for details of how to use it. Look for Script Commands topic
Offline
Pages: 1