# 	
# Placement and Precedence
#
# The metadata.properties file applies to all files and subdirectories in the directory where it is found, including the root directory for SQL scripts.
# Additional metadata.properties files can be used in the subdirectories. A property set in a subdirectory overrides the same property set in a parent directory.
#
#
# The following properties can be set in the metadata.properties file:
#
# disablePropertySubstitution - If 'true' - disables variable substitution performed by packager prior to packaging script.  Default value 'false'.
#
# disableSqlParser   - This is only for Oracle.  Overrides the project option enableSqlParser=true.  There is no effect if the project-level setting is enableSqlParser=false.  
#                      This property previouslycan controlledbe whetherused you can reuse a filename. The default value was 'false', but it is now deprecatedin metadata.properties for folders that use packaging method DIRECT or SQLFILE.
#
# labels archive            - DEPRECATEDOne startingor with Datical DB v4.37. Use rerunnable instead.
#               more labels that identify this set of changes so they can be easily identified and deployed as a group
#       This property previously controlled whether files in the data_dml directory get copied to the archive directory.  
#  labelName[,labelName...]
#
# contexts           - One or more context names to associate a changes Thewith defaultspecified valueenvironments.
was# 'true', but now it is deprecated. # # rerunnable         - Classify SQL scripts as rerunnable (true) or non-rerunnable (false). Use it in place of the [archive] and [allowRepackaging] properties contextName[,contextName...]
#
# allowRepackaging   - DEPRECATED starting with Datical DB v4.37. Use [rerunnable] instead.
#                      This Setproperty rerunnablepreviously tocontrolled 'true'whether or 'false':
#               you can reuse a filename. The default value was 'false', but it is now deprecated.
#
# archive           true - SQLDEPRECATED codestarting filewith isDatical notDB archivedv4.37. ItUse canrerunnable be repackagedinstead.
#                      This property previously controlled falsewhether files -in SQLthe codedata_dml filedirectory isget archived.copied Itto cannotthe bearchive repackageddirectory. # 
#                      If not set, the value is assigned basedThe ondefault itsvalue type (the folder wherewas 'true', but now it is placed in SCM):deprecated.
#
# rerunnable         - Classify SQL scripts as rerunnable (true) or non-rerunnable (false). Use it in place of the [archive] ddland - rerunnable=false[allowRepackaging] properties.
#                      Set rerunnable to  data_dml - rerunnable=false'true' or 'false':
#                          ddl_directtrue - rerunnable=falseSQL #code file is not archived. It can be repackaged.
#                 sql_direct - rerunnable=false #      false - SQL code file is archived. It cannot be repackaged.
#
#         sql - rerunnable=false #          If not set, the value is assigned based on its type (the folder where it is procedureplaced - rerunnable=truein SCM):
#                          packageddl - rerunnable=truefalse
#                          packagebodydata_dml - rerunnable=truefalse
#                          functionddl_direct - rerunnable=truefalse
#                          triggersql_direct - rerunnable=truefalse
#                          viewsql - rerunnable=truefalse
# #                      Important: although the useprocedure of archive and allowRepackaging are allowed, they are deprecated.
#  - rerunnable=true
#                    In addition, the following combinations of settingspackage now cause an error during packaging:- rerunnable=true
#                          archive=truepackagebody and- allowRepackagingrerunnable=true
#                          archive=falsefunction and- allowRepackagingrerunnable=falsetrue
#
#                          trigger - rerunnable=true
#      Also   you can use Flexible Folder Names. When you use flexible folder names it is important to specify rerunnableview correctly.
#- rerunnable=true
#
# packageMethod      - Specifies how to package the file. One of 'convert', 'ddl_direct', 'direct', 'data_dml', 'sqlfile', 'storedlogic', 'ssis'.
#              Important: although the use of archive and allowRepackaging are allowed, they are deprecated.
#         Packager further parses storedlogic files to determine their type, one of 'function', 'procedure', 'package', 'packagebody', 'trigger', 'view'.
#          In addition, the following combinations of settings now cause an error during packaging:
#             Use  the 'changelog' value when packaging Liquibase changelogs. They are processed differently thanarchive=true SQL scripts.and allowRepackaging=true
#    # ignore             - If 'true' - skip files in this directoryarchive=false and all subdirectories and do not process them.
#
# schemaName allowRepackaging=false
#
#                    - Schema nameAlso oryou comma-separatedcan listuse ofFlexible schemaFolder namesNames. #When you use flexible folder names it is important to specify rerunnable correctly.
#
#
# packageMethod      Use- eitherSpecifies ahow literalto valuepackage orthe afile. property.One The property must exist in the changelogof 'convert', 'ddl_direct', 'direct', 'data_dml', 'sqlfile', 'storedlogic'.
#                      IfPackager youfurther useparses fully-qualifiedstoredlogic objectfiles namesto indetermine SQLtheir scriptstype, theone schema names in the SQL scripts must match the schema names in the projectof 'function', 'procedure', 'package', 'packagebody', 'trigger', 'view'.
#                      PackagerUse returnsthe an'changelog' errorvalue ifwhen itpackaging encountersLiquibase achangelogs. schemaThey referenceare thatprocessed isdifferently notthan defined in the projectSQL scripts.
#
# ignore                     For multi-database projects set, schemaName in the form <database>.<schema>.
#                      Starting in version 5.4, you can use a wildcard for the schema: <database>.*.
#            If 'true' - skip files in this directory and all subdirectories and do not process them.
#
# schemaName         - Schema name or comma-separated list of schema names.
#           This capability allows you to manage all SQL scripts for the databaseUse ineither a singleliteral folder.value #
#            or a property. The property must exist in the changelog.
#          WARNING #           If you use fully-qualified object names in SQL scripts, the schema Donames notin the useSQL [schemaName]scripts ifmust youmatch arethe using databaseBackupMode=on_demandschema names in deployPackager.propertiesthe project.
# # versionStrategy    - Specifies how to deploy existing versions of changesets if multiple versions are available to deploy. #Packager returns an error if it encounters a schema reference that is not defined in the project.
#
#    Values are not case-sensitive.  #             For multi-database projects set, schemaName in the form <database>.<schema>.
#    deployAll - Deploy all eligible versions in the order they appear in changelog.xml. Default value. #   Starting in version 5.4, you can use a wildcard for the schema: <database>.*.
#                      This hascapability beenallows theyou strategyto usedmanage historicallyall (before versioning).
#        SQL scripts for the database in a single folder.
#
#                  deployLatest - deploy only the latest eligible version. 
WARNING
# #                     Do Ifnot versionStrategy isuse set[schemaName] toif anyyou otherare value, processing stops with an errorusing databaseBackupMode=on_demand in deployPackager.properties.
#
# versionStrategy    - Specifies how to deploy existing versions of changesets if multiple versions are available to deploy.
A# changeset is eligible to deploy if it meets criteria set in the deploy operation (label expression). # # # The following propertyValues isare only allowed in the root directory (sqlScmSQLBaseDir) and is not allowed in the subdirectories:
#
# folderOrdernot case-sensitive. 
#                  - Comma separated list of folder names to enforcedeployAll the- packageDeploy orderall ofeligible files.versions Thisin canthe beorder usedthey #appear in changelog.xml. Default value.
#                 when packageMethod ordering (deployPacakger property) is insufficient. # # ### Microsoft SQL Server ### # # SQL Server Integration Services (SSIS) relatedThis propertieshas #been #the ssisPkgNamestrategy used historically (before versioning).
#   - Name of an SSIS package file, including extension (.dtsv) # # ssisConfig         - Name ofdeployLatest an- SSISdeploy configurationonly file,the includinglatest extensioneligible (version.dtsConfig) 
#
# ssisDestPath       - Destination directory under SSISDB in the SQL Server database. # # ssisDestType  If versionStrategy is set to -any Howother deployedvalue, SSISprocessing filesstops are stored on the destination SQL Serverwith an error.
#                      A Defaultchangeset is 'SQL'eligible -to storedeploy theif filesit inmeets thecriteria SQLset Serverin databasethe ondeploy theoperation destination(label serverexpression).
#
#
ssisPkgName# The following property is only allowed in -the Name of an SSIS package file (.dtsx)
#
# ssisProjectName    - Name of anSSIS project file (.ispac)root directory (sqlScmSQLBaseDir) and is not allowed in the subdirectories:
#
# ssisSupportFileDestPathfolderOrder - #      - Comma separated list of folder names to enforce the package order of files. This can Windowsbe sharedused
drive# destination for support files that accompany an SSIS package file (.dtsx) #          when packageMethod ordering (deployPacakger property) is insufficient.
#
#
### Microsoft SQL Example: \\SSIS-TEST\SSIS_SHAREDServer ###
#

labels=
contexts=
rerunnable= 
packageMethod=
schemaName=
versionStrategy=
disablePropertySubstitution=