GeezerVison

when there are several numbers with different precision and we make use of package-level nested table types

…/cursor_error_handling

…/cursor_error_handling

…roduce_testing_with_accurate_grants

# Conflicts:
#	docs/about/authors.md
#	docs/about/license.md
#	docs/about/project-details.md
#	docs/about/support.md
#	docs/index.md
#	docs/userguide/advanced_data_comparison.md
#	docs/userguide/annotations.md
#	docs/userguide/best-practices.md
#	docs/userguide/coverage.md
#	docs/userguide/exception-reporting.md
#	docs/userguide/expectations.md
#	docs/userguide/getting-started.md
#	docs/userguide/install.md
#	docs/userguide/querying_suites.md
#	docs/userguide/reporters.md
#	docs/userguide/running-unit-tests.md
#	docs/userguide/upgrade.md
#	source/core/ut_utils.pks

expectations/binary/test_equal
expectations/binary/test_expect_to_be_less_than
expectations/test_expectation_anydata
expectations/test_expectation_processor

expectations/binary/test_be_less_or_equal

changing name of function to more meaningful.

expectations/binary/test_be_greater_or_equal
expectations/binary/test_be_greater_than
expectations/unary/test_expect_not_to_be_null

Passing username implicit into ut_test_runner.

expectations/unary/test_expect_to_be_empty
expectations/unary/test_expect_to_be_null
expectations/unary/test_expect_to_be_true_false
expectations/unary/test_expect_to_have_count

Adding dummy type for testing.

Added new user to `template.env.sh`

Updated `install.md`

…ub.com:utPLSQL/utPLSQL into feature/introduce_testing_with_accurate_grants

Structure of test cases is affected since new PL/SQL package is created which is also used in the whole run.

…_reporter

Feature/add warnings to realtime reporter

Fixed issue with utPLSQL failing to run when schema contains package named the same as schema owning it.
It is now possible to have utPLSQL test package like this:
```
create or replace package some_schema.some_schema as
  --%suite

  --%test
  procedure sample_test;
end;
/

create or replace package body some_schema.some_schema as
   procedure sample_test is begin ut.expect(1).to_equal(1); end;
end;
/
```

The tests from the package can be invoked by calling:
`exec ut.run('some_schema.some_schema');`

If only schema is provided, all test packages in schema are executed.
`exec ut.run('some_schema');`

Resolves #569
Resolves #885

…ents.

Timing before change (with dbms_lob.read):
`clob_to_table - Took:+000000000 00:00:00.012957000`
After change:
`clob_to_table - Took:+000000000 00:00:00.001236000`
Speed improved by order of magnitude.

…_resolve

Removed dependency on `dbms_utility.name_resolve`.

Fixed issue with parsing via trigger source with leading comments

* Initial checkin.
General skelet of code

* Adding json tree parsing.
Enabling 12.2

* Update tests.
Update sonar rules.

* small fixes

* PHASE 2:
Moving diff into temp table and init data compare during compare implementation to avoid finding same differences twice
Adding have count and negated have count matcher.l

* Added more complex tests.
Added test when extract a piece from two different jsons.
Small fixes to code on same hierarchy parent arrays

* Update mddocs
Fix to json traverse array when object is element of array, the element name is content of object which can be different order but same semantic content.

* Fixing sonar

* Switch to use supertype

* PHASE3 : Adding a functionality for install in pre 12.2

* PHASE3 : Adding a functionality for install in pre 12.2

* PHASE3 : Adding a functionality for install in pre 12.2

* PHASE3 : Adding a functionality for install in pre 12.2

* PHASE3 : Adding a functionality for install in pre 12.2

* PHASE3 : Adding a functionality for install in pre 12.2

* update tests

* Update set define off

* Code cleanup

* fix slash

* Creating a dummy specs and removing conditional compilation for code cleanup

* PR fixes.

* Reverting development script changes.

* Refactored JSON code.
Changed formatting of JSON-diff output.
Changed date formats.

* Fixed install on Oracle < 12.2