At 10:04 AM 9/03/2010, Gábor Török wrote: >Hi! I understand your point. What is the preferred solution to make scripts >work with FbBatchExecution without modifying them in a way to break >compatibility with other tools? For example I could process the script and set >connection parameters after parsing it with FbScript.
You seem to be looking at this in a strange way. The server itself does not process scripts. A script component is merely a container for the application execute a series of DSQL statements in sequence. The application connects just as usual, with the required connection charset and dialect, and fires off these statements one by one. The smarter ones provide optional exception handling. Most script components are written just to ignore non-SQL sentences such as SET NAMES and SET SQLDIALECT, purposely to enable you to execute a script that was created for use with isql. I'd be surprised if FbScript doesn't provide this too. Otherwise there is nothing special about a script. SET NAMES and SET SQLDIALECT are for interactive use within an isql shell. Scripts do not take parameters. The fact is that isql has a command-line mode, whereby you can pass parameters to set things like connection charset and sql dialect on switches, along with an -i switch for a script to execute. When isql runs from the command line or a batch file, it does understand the SET commands, but you can set them either way for isql. Helen ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
