Versions Compared

Old Version 1

changes.mady.by.user Anonymous

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

In some cases you may need to override the default packaging behavior for SQL script processing order.

...

  • DEFAULT - Use the default packaging order. See also Processing Order in Fixed Folder Names. 
    • Commit time - Process all files committed at the same as a group. If multiple groups are found, process them in commit-time order. 
    • File type (folder) - Within a commit group, process files in folder order (corresponds to object type)
    • Alphabetical by filename  - Within a folder, process files in alphabetical order. 
  • PACKAGEMETHOD - Do not consider commit order. See also Flexible Folder Names. 
    • packageMethod setting -  Process in order of packageMethod (set in metadata.properties)
    • Alphabetical by filename - Within a packageMethod, process files in alphabetical order.
  • ALPHANUMERIC - Process in alphabetical order only. Do not consider commit time or packageMethod. 
    • That the name of the folder plus the filename are included when using alphanumeric packageOrderStrategy. 
    • The primary sorting is alphanumeric by name of the folder, and the secondary sorting is alphanumeric by name of the file within each folder.

Specifying Folder-Processing Order in metadata.properties

...

  1. Place a metadata.properties file in the top of the SQL code tree. It must correspond to the directory specified in the sqlScmSQLBaseDir property in the deployPackager.properties file.  
  2. Use the folderOrder property in that metadata.properties file to specify a list of folders.  Files in the folder are pulled to the front of the list of files to package, ahead of files in other directories.  .  (Note that if you use custom folderOrder, the commit time will not be considered as part of the overall ordering.)

Examples: Specifying Packaging in a Multiple Schema Project

Each entry in the comma-separated list of values in the folderOrder property is used as a filter on the path to the file. 

  • Files matching the filter are moved to the front of the list of files to package. The process is repeated for each value, in order.
  • The sorting takes place after the baseline packaging order is determined using the packageOrderStrategy property. 
  • Any file in the list that does not match one of the filters is processed after the ordered files and according to the packageOrderStrategy setting.and according to the packageOrderStrategy setting
  • This method is intended as an extension to be used with the PACKAGEMETHOD and ALPHANUMERIC strategies. (It is not intended to be used with DEFAULT stategy.)

SQL Code Folder Organization and Packaging Strategy for the Examples

...

Code Block
titleInitial File Order Based on 'packageOrderMethod' setting of 'PACKAGEMETHOD'
     PACKAGING ORDER FOR COMMIT FILES:
     ---------------------------------
     packageOrderStrategy: PACKAGEMETHOD
     folderOrder:

     COMMIT ID    PACKAGE METHOD    FILENAME/ROLLBACKFILE
     da62531      convert           schema1\constraints\SCHEMA1_FKS.sql
     da62531      convert           schema1\constraints\SCHEMA1_PK_UQ_CONSTRAINTS.sql
     da62531      convert           schema1\indexes\SCHEMA1_I_NAME.sql
     da62531      convert           schema1\tables\SCHEMA1_T_BORROWING.sql
     da62531      convert           schema1\tables\SCHEMA1_T_CUSTOMER.sql
     da62531      convert           schema1\tables\SCHEMA1_T_CUSTOMER_RATING.sql
     da62531      convert           schema1\tables\SCHEMA1_T_EXEMPLAR.sql
     da62531      convert           schema1\tables\SCHEMA1_T_FILM.sql
     da62531      convert           schema1\tables\SCHEMA1_T_GENRE.sql
     da62531      convert           schema1\tables\SCHEMA1_T_MEDIUM.sql
     da62531      convert           schema1\tables\SCHEMA1_T_ORDER.sql
     da62531      convert           schema2\constraints\SCHEMA2_FKS.sql
     da62531      convert           schema2\constraints\SCHEMA2_PK_UQ_CONSTRAINTS.sql
     da62531      convert           schema2\indexes\SCHEMA2_I_NAME.sql
     da62531      convert           schema2\tables\SCHEMA2_T_BORROWING.sql
     da62531      convert           schema2\tables\SCHEMA2_T_CUSTOMER.sql
     da62531      convert           schema2\tables\SCHEMA2_T_CUSTOMER_RATING.sql
     da62531      convert           schema2\tables\SCHEMA2_T_EXEMPLAR.sql
     da62531      convert           schema2\tables\SCHEMA2_T_FILM.sql
     da62531      convert           schema2\tables\SCHEMA2_T_GENRE.sql
     da62531      convert           schema2\tables\SCHEMA2_T_MEDIUM.sql
     da62531      convert           schema2\tables\SCHEMA2_T_ORDER.sql
     da62531      ddl_direct        schema2\complex_tables\SCHEMA1_N_CUSTOMER.sql
     da62531      storedlogic       schema1\views\SCHEMA1_V_CUSTOMER.sql
     da62531      storedlogic       schema1\views\SCHEMA1_V_CUSTOMER_HAS_FILM.sql
     da62531      storedlogic       schema2\views\SCHEMA2_V_CUSTOMER.sql
     da62531      storedlogic       schema2\views\SCHEMA2_V_CUSTOMER_HAS_FILM.sql
     da62531      direct            schema1\grants\SCHEMA1_GRANT_SELECT.sql
     da62531      direct            schema1\types\SCHEMA1_UDTS.sql
     da62531      direct            schema2\types\SCHEMA2_UDTS.sql

...

Code Block
title'types' First File Order
     PACKAGING ORDER FOR COMMIT FILES:
     ---------------------------------
     packageOrderStrategy: PACKAGEMETHOD
     folderOrder: types

     COMMIT ID    PACKAGE METHOD    FILENAME/ROLLBACKFILE
     da62531      direct            schema1\types\SCHEMA1_UDTS.sql					
     da62531      direct            schema2\types\SCHEMA2_UDTS.sql						 
// ------------------------------------------------------------------------------------------'types' have moved from the bottom to the top of the Packaging Order
     da62531      convert           schema1\constraints\SCHEMA1_FKS.sql
     da62531      convert           schema1\constraints\SCHEMA1_PK_UQ_CONSTRAINTS.sql
     da62531      convert           schema1\indexes\SCHEMA1_I_NAME.sql
     da62531      convert           schema1\tables\SCHEMA1_T_BORROWING.sql
     da62531      convert           schema1\tables\SCHEMA1_T_CUSTOMER.sql
     da62531      convert           schema1\tables\SCHEMA1_T_CUSTOMER_RATING.sql
     da62531      convert           schema1\tables\SCHEMA1_T_EXEMPLAR.sql
     da62531      convert           schema1\tables\SCHEMA1_T_FILM.sql
     da62531      convert           schema1\tables\SCHEMA1_T_GENRE.sql
     da62531      convert           schema1\tables\SCHEMA1_T_MEDIUM.sql
     da62531      convert           schema1\tables\SCHEMA1_T_ORDER.sql
     da62531      convert           schema2\constraints\SCHEMA2_FKS.sql
     da62531      convert           schema2\constraints\SCHEMA2_PK_UQ_CONSTRAINTS.sql
     da62531      convert           schema2\indexes\SCHEMA2_I_NAME.sql
     da62531      convert           schema2\tables\SCHEMA2_T_BORROWING.sql
     da62531      convert           schema2\tables\SCHEMA2_T_CUSTOMER.sql
     da62531      convert           schema2\tables\SCHEMA2_T_CUSTOMER_RATING.sql
     da62531      convert           schema2\tables\SCHEMA2_T_EXEMPLAR.sql
     da62531      convert           schema2\tables\SCHEMA2_T_FILM.sql
     da62531      convert           schema2\tables\SCHEMA2_T_GENRE.sql
     da62531      convert           schema2\tables\SCHEMA2_T_MEDIUM.sql
     da62531      convert           schema2\tables\SCHEMA2_T_ORDER.sql
     da62531      ddl_direct        schema2\complex_tables\SCHEMA1_N_CUSTOMER.sql
     da62531      storedlogic       schema1\views\SCHEMA1_V_CUSTOMER.sql
     da62531      storedlogic       schema1\views\SCHEMA1_V_CUSTOMER_HAS_FILM.sql
     da62531      storedlogic       schema2\views\SCHEMA2_V_CUSTOMER.sql
     da62531      storedlogic       schema2\views\SCHEMA2_V_CUSTOMER_HAS_FILM.sql
     da62531      direct            schema1\grants\SCHEMA1_GRANT_SELECT.sql

...