You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
set echo on;
set bail on;
show domain;
show database;
Run it via batch:
@echo off
C:\MIX\firebird\fb30\isql /:e30 -i show-grant-when-bail-on.sql
if errorlevel 1 echo Error occured inside SQL script.
Output will be:
set bail on;
show domain;
There are no domains in this database
Error occured inside SQL script.
Command 'show database;' (and all subsequent ones) was not executed because of set bail = ON. But this case (when there is no domain or other object type) not neccessary should be considered as ERROR!
Can ISQL be improved in such way that message "There are no <...> in this database" will be WARNING rather than ERROR ? (of course it should be redirected in STDERR as before).
The text was updated successfully, but these errors were encountered:
1) Your sample requires two additive commands every time I need to show objects.
2) I do not offer to ignore absence of <X>, just to consider it as warning.
Submitted by: @pavel-zotov
Consider this script:
set echo on;
set bail on;
show domain;
show database;
Run it via batch:
@echo off
C:\MIX\firebird\fb30\isql /:e30 -i show-grant-when-bail-on.sql
if errorlevel 1 echo Error occured inside SQL script.
Output will be:
set bail on;
show domain;
There are no domains in this database
Error occured inside SQL script.
Command 'show database;' (and all subsequent ones) was not executed because of set bail = ON. But this case (when there is no domain or other object type) not neccessary should be considered as ERROR!
Can ISQL be improved in such way that message "There are no <...> in this database" will be WARNING rather than ERROR ? (of course it should be redirected in STDERR as before).
The text was updated successfully, but these errors were encountered: