We want test the first time installing GITORA (V 3.1) and we are a bit confused about the software quality.
When we installed the script 02_GITORA.sql the logfile will show many invalid compiled sources. I know after we recompiled the hole schema almost all is already valid. But it makes no good feel . Perhapes it is possible to sort all your DML's so that the invalid message in the log is minimized.
But also after recompiling some DB-Object are still invalid. I see in your Gitora.xml you don't use the table/view GO_SCHEMA_V yet. But if I correctly understand the Trigger GO_SCHEMA_V_IOT would make adding or removing repositories. Is that functionality which is not working yet really not important?. When not, it should not visible for your customers, because it makes not a good feeling to install it.
One point more
In your description you write "Open 02_GITORA.sql and replace all occurrences of @GITORA_SCHEMA@ keyword
with the schema name that Gitora will be installed"
But that is there so exactly not found. There is only @GITORA_SCHEMA_NAME@ found.
Thank you for the feedback. We did not optimize the installation code to produce fewer log records. Our goal was to install Gitora successfully in the end and based on your message I think Gitora is successfully installed.
Given that Gitora is mostly installed on very restrictive corporate envrionments, there are so many different platforms, versions, access rights for different components involved that our priorty was getting all that working properly first. Unfortunately, reducing the number of log entires we generate was not high in the list.
Now that we have about 95% success rate with installations, I guess we can look at ways to improve the process and I really appreciate the feedback on reducing the number of log entries.
Regarding the GO_SCHEMA_V view. That view is not used by Gitora. It is just an object we forgot to remove from the installation script. You can drop it if you'd like.
Thank you for letting us know. We'll fix the error in the document.