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.
I am working professionally with databases for over 15 years now and have a huge focus on Oracle – but I really keep forgetting how to update a table with values of a different one (this is one thing which is so much easier in SQL Server by the way).
Therefore let’s assume we have a table containing planets and one containing garrisons which are on these planets.
|Garrison ID||Planet Name||Planet Faction|
We would now like to have a new column in the garrisons table which can contain a name.
alter table garrisons add name varchar2(300)
The imperial side now has a request to update all their garrisons with a name according to this schema: <PlanetName> (<Garrison ID>)(more…)
If it comes to testing updatable views, the use of nested tables from ROWTYPE records in combination with utPLSQL’s cursor comparison is invaluable.
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.