User Tools

Site Tools


configure_lure_to_create_pending_patch_files_automatically

Differences

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

Link to this comparison view

configure_lure_to_create_pending_patch_files_automatically [2013/07/30 08:04]
admin created
configure_lure_to_create_pending_patch_files_automatically [2013/07/30 08:07] (current)
admin
Line 9: Line 9:
 During export Lure will now automatically create versioned patch files for all table changes. Consider for example a table with name COMPANY. Lure will create a versioned patch file as follows: During export Lure will now automatically create versioned patch files for all table changes. Consider for example a table with name COMPANY. Lure will create a versioned patch file as follows:
  
-''​ +  ​COMPANY.table.lsql.r34.lpatch-pending 
-COMPANY.table.lsql.r34.lpatch-pending +
-''​+
 The version of the patch file (34 in the above example) will be set equal to the SVN head revision. Lure cannot create the versioned patch file unless the table source is checked out within the project directory. Lure compares the newly exported table source code with the table source code of the checked out SVN base revision and adds the corresponding ALTER TABLE statements to the patch file. The version of the patch file (34 in the above example) will be set equal to the SVN head revision. Lure cannot create the versioned patch file unless the table source is checked out within the project directory. Lure compares the newly exported table source code with the table source code of the checked out SVN base revision and adds the corresponding ALTER TABLE statements to the patch file.
  
Line 20: Line 19:
 Pending patch files can be approved from within Lure Stage via the context menu. Right click on the pending patch file from within the Lure Project Explorer view and select "​Approve Patch" from the popup menu. This will change the name of the file to: Pending patch files can be approved from within Lure Stage via the context menu. Right click on the pending patch file from within the Lure Project Explorer view and select "​Approve Patch" from the popup menu. This will change the name of the file to:
  
-COMPANY.table.lsql.r34.lpatch+  ​COMPANY.table.lsql.r34.lpatch
  
 The patch files is now approved and will be used in subsequent import operations. The patch files is now approved and will be used in subsequent import operations.
Line 28: Line 27:
 Although pending patch files will be ignored during import, they will be executed (and therefore tested) in patch test mode. Although pending patch files will be ignored during import, they will be executed (and therefore tested) in patch test mode.
  
-Do note: Any statements created by Lure in the patch file have to be carefully reviewed and updated by the developer. Lure does not correctly recognize when a column or table name was renamed. Lure will instead interpret this as a drop (column/​table) and add (column/​table). Also, currently Lure can only add ALTER statements for columns. Any other table property or storage changes have to be added manually in the patch file.+**Do note:** Any statements created by Lure in the patch file have to be carefully reviewed and updated by the developer. Lure does not correctly recognize when a column or table name was renamed. Lure will instead interpret this as a drop (column/​table) and add (column/​table). Also, currently Lure can only add ALTER statements for columns. Any other table property or storage changes have to be added manually in the patch file.
  
configure_lure_to_create_pending_patch_files_automatically.txt · Last modified: 2013/07/30 08:07 by admin

Page Tools