...
- portal_sql is the name of your repository,
- sql_code is the name of the directory where the packager will look for new/modified .sql files to package, this directory is reference in the deployPackager.properties in your DaticalDB project
- the sub-directories represent the different kinds of SQL scripts to package. The
- the process order for a commit when using fixed folder names is the following: ddl, ddl_direct, view, function, procedure, package, packagebody, trigger, sql, sql_direct and finally data_dml folder
- the process order for a commit when using flexible folders is: convert, ddl_direct, storedlogic, sqlfile, direct, and finally data_dml . More packageMethod
- more details cane be found at Placing Files in the SCM Repository.
metadata.properties
In each directory under the top level one (sql_code in this example), you can create configuration file named metadata, where you can pass some additional directives to the packager (like additional label or context).
...
- check out to a sub-directory: portal_ddb
- Don't trigger a build on commit notification (if you have a CI, you do not want to start a new build when the DaticalDB project is modified)
- Check out to specific local branch: master (as the chanes changes are cumulative, there is no need for a branch)
...