Objects in oracle can be used to create nested table collections, which are accessible from SQL.
However, to change these objects once referenced by a table type can be very annoying unless you use the force.
#100CodeExamples: Cursor-comparison is one of the most powerful features of utPLSQL.
To model our expectation, we can not only use SELECT FROM DUAL but also the much more powerful user-defined types and Nested Table-collections.
#100CodeExamples – Implement some different force-sensitive beings with PL/SQL objects.
This is the first of several examples showing the object-oriented capabilities of PL/SQL.
#100CodeExamples – PL/SQL BOOLEAN to INT
For Oracle doesn’t know a BOOLEAN SQL-Type, we must find a smooth way to convert PL/SQL-BOOLEAN to INT
#100CodeExamples – SYSDATE vs. CURRENT_DATE
I had a very strange problem yesterday where #utPLSQL cli showed different test outcomes than running the tests from my IDE. Here’s the reason.
#100CodeExamples – utPLSQL’s Suite Hierarchy in action.
A great tool to structure tests, avoid duplication, give context and improve performance.
#100CodeExamples – How to put dynamic values in a String with #PLSQL.
One possibility: the sys-package UTL_LMS
#100CodeExamples – Unit-Tests for Primary/Secondary Lookup with the Cursor Comparison capabilities of utPLSQL.
#100CodeExamples – A challenge to learn and teach.
My first example today: How to do a Primary/Replica lookup (in SQL) which I can query with the ID of any entry.