Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
uninstall sql script not comprehensive #673
We are using TeamCity to install and uninstall utPLSQL each testing cycle in the application owner schema.
As part of our database build, we are checking for modified objects and I noticed we are incurring leftover objects from the framework after the uninstall script is executed.
Can you please advise if this is a bug or intended behavior? I have attached my modified copy of the uninstall.sql which seems to deal with it.
Additionally: We are on version 3.0.4 of the framework but I couldn't find any bug addressed in the versions since. There also seem to be types leftover when actually executing tests (not captured in the recreation steps below).
Thanks for the quick response:
@lwasylow, I'll give that a shot.
@jgebal, I agree there is no harm. But they are installed as part of the framework. If I uninstall the framework, should they remain? If so, to what end? Is this to avoid damaging analysis that potentially already exists in those tables unrelated to utPLSQL? Should we be directing this to a separate store somehow? I imagine this is one of the reasons the documentation suggests installing to a separate schema. How about mentioning that in the documentation if we prefer not modifying the uninstall?
Good point @lwasylow
If you do: uninstall, install, test in each run, it would probably be better to switch to: install, test, uninstall.
Also, it would be a good idea to use docker or some kind of DB snap, so you can just have a baseline (with utPLSQL installed) and run your tests without need to reinstall framework.
I would also encourage to install framework into it's own schema (as a shared library).
7 rows selected.
@jgebal: I may not have been clear in my first post. After installing the application schema, we install, test, uninstall as you suggest.
@SpotMeFive - thanks for the kudos on the work we did.
Was there some historical reason why there is each object named in the uninstall.sql script?