From 63b01e3131a26a99044bb8f728f0555628cca510 Mon Sep 17 00:00:00 2001 From: Ytbarek Hailu Date: Mon, 24 Nov 2025 12:34:23 -0800 Subject: [PATCH] updated documentation --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e3c687a..5e039d6 100644 --- a/README.md +++ b/README.md @@ -104,7 +104,7 @@ Each object will have a single SQL to track the changes applied to the given obj For example if you have a view named `SAMPLE_VIEW` in schema `MY_SCHEMA` in database `MY_DATABASE`, then the script file should be named `SAMPLE_VIEW.SQL` and should be placed in the directory `[scripts_root]/main/MY_DATABASE/MY_SCHEMA/VIEWS/SAMPLE_VIEW.SQL`. The structure and content of the scripts will defer based on the type of script. This tool categorizes script in to 2 types named State script and Migration script. #### 1. State Script -This type of script is used for object types of Views, UDF, Stored Procedure, File formats and Pipes. +This type of script is used for object types of VIEWS, UDF, PROCEDURES, FILE FORMATS, PIPES AND MASKING POLICIES. In this type of script you define the current state(desired state) of the object. When a change is made to the script, DLSync replaces the current object with the updated definition. These types of scripts must always have `create or replace` statement. Every time you make a change to the script DLSync will replace the object with the new definition.