v1.4.2

What's Changed

• Fix #202 - no empty list is passed to the database module if no sql params were specified. Fixes an error if the database module doesn't accept an empty list as parameters.
• Fix #184 - Improvements in parsing the PL/SQL script files.
• The keyword Execute SQL Script has a new parameter split now - setting it to False disables splitting the SQL script into statements. In this case the entire script content will be passed to the database module for execution.
• The keyword Execute SQL String has a new parameter omitTrailingSemicolon - for explicit instruction, if the trailing semicolon (;) at the SQL string end should be removed or not.
  • Setting it to False will fix an error, if the Oracle database exceptionally requires a semicolon at the end of the PL/SQL block. More details available here.
  • If not specified, it's decided based on the current database module in use. For Oracle, the semicolon is removed by default.
• #201 - improved docs of the Query keyword - added a note, that result values might be not always tuples (depends on the database module)

Full Changelog: v1.4.1...v1.4.2

Thanks a lot to all contributors!

@amochin