User Tools

Site Tools


include_and_exclude_filters

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

include_and_exclude_filters [2013/07/25 21:00]
127.0.0.1 external edit
include_and_exclude_filters [2013/07/29 19:03] (current)
admin
Line 7: Line 7:
 During export Lure applies all include/​exclude filters as set up in the Lure property files. ​ During export Lure applies all include/​exclude filters as set up in the Lure property files. ​
  
-The easiest way to set up the include/​exclude filters is to use the Lure Configuration Editor. Each object type (e.g. tables or views) has its own set of filters. Each parameter (for each object type) can be set to a comma separated list of patterns to match. Lure matches filter patterns on the names of extracted source files but excluding the extension.+The easiest way to set up the include/​exclude filters is to use the Configuration Editor ​within Lure Stage. Each object type (e.g. tables or views) has its own set of filters. Each parameter (for each object type) can be set to a comma separated list of patterns to match. Lure matches filter patterns on the names of extracted source files but excluding the extension.
  
 Filter patterns can be configured using the characters "​*"​ and "?",​ where "​*"​ matches zero or more characters and "?"​ matches a single character. For example the setting: Filter patterns can be configured using the characters "​*"​ and "?",​ where "​*"​ matches zero or more characters and "?"​ matches a single character. For example the setting:
Line 45: Line 45:
 This behaviour of filters is intended so that sensible filters can be set up globally by the technical lead but can still be overridden by each individual developer. ​ This behaviour of filters is intended so that sensible filters can be set up globally by the technical lead but can still be overridden by each individual developer. ​
  
-Another case where this behaviour is useful is for table data files. By default no data files for tables will be exported. This is desirable since generally it does not make sense to have table data in the version control system. But in many database applications there is a smallish ​subset of tables that contain meta data which need to be the same in all instances of the application and typically only change with new releases of the application. In order to add the data for these meta data tables to the version control system simply create the data files for these tables manaullly. Subsequent Lure export operations will export the table data to the file.+Another case where this behaviour is useful is for table data files. By default no data files for tables will be exported. This is desirable since generally it does not make sense to have table data in the version control system. But in many database applications there is a small subset of tables that contain meta data which need to be the same in all instances of the application and typically only change with new releases of the application. In order to add the data for these meta data tables to the version control system simply create the data files for these tables manaullly. Subsequent Lure export operations will export the table data to the file.
    
 Alternatively use the command option ''​%%--ignore-filters%%''​ to override the filters. Alternatively use the command option ''​%%--ignore-filters%%''​ to override the filters.
    
  
include_and_exclude_filters.txt ยท Last modified: 2013/07/29 19:03 by admin

Page Tools