Currently, when following the README, only dblink is being put into schema pgunit. All functions test_* and type test_results are being created in current (default: public) schema.
This clutters the default and/or the user schema, while there are cleaner means, like putting everything in pgunit schema.
So, the schema pgunit should contain all functions (test_*) and type (test_results) and types related to this test framework (except the specific user defined SQL script). With this one can do DROP SCHEMA pgunit; and everything is cleaned up - instead of doing many times a DROP FUNCTION....
In addition one could consider to "package" everything into a simple PostgreSQL extension.
Currently, when following the README, only dblink is being put into schema pgunit. All functions test_* and type test_results are being created in current (default: public) schema.
This clutters the default and/or the user schema, while there are cleaner means, like putting everything in pgunit schema.
So, the schema pgunit should contain all functions (test_*) and type (test_results) and types related to this test framework (except the specific user defined SQL script). With this one can do
DROP SCHEMA pgunit;and everything is cleaned up - instead of doing many times aDROP FUNCTION....In addition one could consider to "package" everything into a simple PostgreSQL extension.