UTPLSQL vs. ruby-plsql/ruby-plsql-spec – part three – (not) reporting failures I have finished my previous post with comparison of basic reporting capabilities build into UTPLSQL and ruby-plsql frameworks for Oracle unit testing. Additional reporting options for ruby-plsql So far I have been using the ruby-plsql-spec wrapper around RSpec to run unit tests, however ruby-plsql was created in a way, that developer is not limited to… Read More
UTPLSQL vs. ruby-plsql/ruby-plsql-spec – part two (setup and basic reporting) In my previous post I have described the conceptual differences between UTPLSQL and ruby-plsql frameworks for unit testing of Oracle database code. I have used a message_api package and unit tests for that API using both frameworks as an example. In this post I will focus on getting the tests to run and the feedback… Read More
UTPLSQL vs. ruby-plsql/ruby-plsql-spec – part one Foreword Unit Testing is around for quite a while. Since it started to become more and more popular, quite a few tools became available for Oracle database to allow unit testing of the database. There are the UI based tools like Quest Code Tester (now Dell Code Tester for Oracle), Oracle SQL Developer unit testing.… Read More
Oracle MERGE operation – get number of rows inserted / updated deleted Oracle database does not support ability to obtain number of rows inserted/updated/deleted by a merge operation. The only value you can obtain is the total number of rows affected by merge operation. Consider the following example. Setup. Code: All that you can get is the overall number of rows processed by merge statement. So I’ve created… Read More