If I load a script and run it from the SQL view the execution stops
when it finds an empty line.
select * from table1;
select * from table2;
select * from table3;
Only 2 statements would be executed. This makes sense with lots of
inserts or updates or DDL statements, but it works with any SQL
I have ! setted as statement separator, but happens with ; as well.
Any idea why this happens ond if it can be avoided?
Get latest updates about Open Source Projects, Conferences and News.