...
Note: when modifySQL is run, Liquibase has already converted MySQL's DATETIME into Oracle TIMESTAMP, so TIMESTAMP is what needs to be in the replace clause to match against.
Contexts
Liquibase has the concept of a context. When running liquibase, a context can be specified and only changes with this context will be loaded. All liquibase change files should have the appropriate context on them. All liquibase change sets should have the appropriate context specified. Multiple contexts can be specified by separating them with commas. Here is an example:
| Code Block | ||
|---|---|---|
| ||
<changeSet author="KFS51" id="KFSCNTRB-734" context="bootstrap,demo,unit">
<comment>KFSCNTRB-734</comment>
<addColumn tableName="FS_DOC_HEADER_T">
<column name="SECURE_FIELD" type="VARCHAR(255)" />
</addColumn>
</changeSet> |
This is a list of the contexts defined for financials.
| Context | Purpose |
|---|---|
| bootstrap | |
| demo | |
| unit | |
| kc | |
| kc |
Sample Liquibase Scripts
| Code Block | ||
|---|---|---|
| ||
<changeSet author="KFS50" id="KFSMI-6921_CA_ACCT_AUTODEF_ICR_T"> <comment>KFSMI-6921 Create Account and A21SubAccount ICR collection tables</comment> <createTable tableName="CA_ACCT_AUTODEF_ICR_T"> <column name="CA_ICR_ACCT_GNRTD_ID" type="DECIMAL(10,0)"> <constraints primaryKey="true" primaryKeyName="CA_ACCT_AUTODEF_ICR_TP1" /> </column> <column name="OBJ_ID" type="VARCHAR(36)"> <constraints nullable="false" unique="true" uniqueConstraintName="CA_ACCT_AUTODEF_ICR_TC0" /> </column> <column name="VER_NBR" type="DECIMAL(8,0)" defaultValueNumeric="1"> <constraints nullable="false" /> </column> <column name="ACCT_DFLT_ID" type="DECIMAL(10,0)" /> <column name="ICR_FIN_COA_CD" type="VARCHAR(2)" /> <column name="ICR_FIN_ACCT_NBR" type="VARCHAR(7)" /> <column name="ACLN_PCT" type="DECIMAL(35,20)" /> <column name="ACTV_IND" type="VARCHAR(1)" defaultValue="Y" /> </createTable> </changeSet> |
...