When I run this using F5 (Execute as script)
whenever oserror exit 1
start non_existing_file.sql
I get this as a result.
Commit complete.
Given that the file does not exist it seems like I should get an error. I had a coworker run the same in SQL Developer and he got:
Error report -
SP2-0310: Unable to open file “non_existing_file.sql”
Commit
Why doesn’t TOAD do something similar? In TOAD, it appears that everything ran fine - even though it was asked to run a non-existant file. I’ve looked through the options and couldn’t find anything addressing this behavior.