Steven Feuerstein will do some live refactoring in his “Feuertips” episode #13.
However, in order to confidently refactor, one could use some automated tests that ensure the functionality doesn’t change…
It is a common practice to eliminate possible NULL values from your method’s parameters, and in the past I advocated to use subtypes to do this in PL/SQL.
However, it doesn’t work from SQL…
I’ll try to solve the #AdventOfCode2020 with SQL (and PL/SQL if necessary).
First challenge is to find the two numbers of a list that sum up to 2020 and multiply them.
My last example of controlling a sequence to test some default-behavior was not “well-testable” PL/SQL code.
In this example I show how we can achieve a method that is much easier to test, doesn’t require touching internals – all without changing the public API of the method.
A combination of Package global state and Package invalidation can easily lead to ORA-04061 errors, especially in unit-testing situations.
This blog-post explains the problem and shows possible solutions (all with examples)
How to explore some functionality you don’t know but want to change or improve?
Write a unit test with utPLSQL and use the force-manual-rollback param!
#ThanksOGB
How to concatenate a list of Strings in PL/SQL?
This blog-post shows 4 different approaches.
Object Types are a very useful thing when used in PL/SQL, but Oracle even allows us to have them inside a table.
Let’s see how we can put the numeric_strucutre-logic inside the Force Powers table and use indizes on the new column.
Modern SQL and especially PL/SQL is turing complete and can be used to solve every problem, but Oracle SQL Types can help greatly to do it in a much more readable way.
The context-feature of #utPLSQL can greatly help to organize your tests and reduce the setup/teardown time of tests.
Learn how to use them to test the Deathstar security system.
#100CodeExamples