--- a/liquibase.rst Sat Feb 10 01:28:53 2018 +0200
+++ b/liquibase.rst Sat Feb 10 01:30:24 2018 +0200
@@ -11,14 +11,14 @@
Official statement about introducing LiquiBase to existing project are:
- http://www.liquibase.org/documentation/existing_project.html
- Adding Liquibase on an Existing project
+http://www.liquibase.org/documentation/existing_project.html
+ Adding Liquibase on an Existing project
There are two approaches:
- * create full schema definition prior to introducing Liquibase
- * works only with current changes becase Liquibase basically work only with changesets and only
- special supplied instruments care about full schema definition
+* create full schema definition prior to introducing Liquibase
+* works only with current changes becase Liquibase basically work only with changesets and only
+ special supplied instruments care about full schema definition
To create full schema definition in LiquiBase XML changelog format you may run::
@@ -68,15 +68,15 @@
Now my file is safely can be applied to production database without loosing
data and can recreate new schema in empty database.
- * http://www.operatornew.com/2012/11/automatic-db-migration-for-java-web.html
- * http://www.baeldung.com/liquibase-refactor-schema-of-java-app
- * http://www.liquibase.org/documentation/existing_project.html
- * http://www.liquibase.org/tutorial-using-oracle
+* http://www.operatornew.com/2012/11/automatic-db-migration-for-java-web.html
+* http://www.baeldung.com/liquibase-refactor-schema-of-java-app
+* http://www.liquibase.org/documentation/existing_project.html
+* http://www.liquibase.org/tutorial-using-oracle
SQL syntax.
===========
- * http://www.liquibase.org/2015/09/liquibase-without-changelogs.html
+* http://www.liquibase.org/2015/09/liquibase-without-changelogs.html
Generate difference between databases.
@@ -87,8 +87,8 @@
suggest using Hibernate ``hibernate.hbm2ddl.auto=create`` to create clean schema
with Hibernate and compare it with previous one. So you:
- * create empty schema and grand permissions for user
- * register project to new user and schema, for example with Spring config::
+* create empty schema and grand permissions for user
+* register project to new user and schema, for example with Spring config::
<bean id="dataSource"
class="org.apache.commons.dbcp2.BasicDataSource" destroy-method="close">
@@ -116,11 +116,11 @@
</property>
</bean>
- * run Hibernate initialisation code via test or application deploy so
- ``hibernate.hbm2ddl.auto=create`` trigger to new schema generation.
+* run Hibernate initialisation code via test or application deploy so
+ ``hibernate.hbm2ddl.auto=create`` trigger to new schema generation.
- * configure Maven ``pom.xml`` with paths and authentication data to old and new
- schema::
+* configure Maven ``pom.xml`` with paths and authentication data to old and new
+ schema::
<plugin>
<groupId>org.liquibase</groupId>
@@ -161,9 +161,9 @@
<changeLogFile>${basedir}/src/main/resources/sql/master.xml</changeLogFile>
- * Review diff in ``changelogDiff.xml`` after::
+* Review diff in ``changelogDiff.xml`` after::
- $ mvn liquibase:diff
+ $ mvn liquibase:diff
Resulted ``changelogDiff.xml`` may be registered to project with ``schema_v1.1``
schema state.
@@ -182,7 +182,7 @@
$ mvn liquibase:updateSQL
-TODO:
+TODO::
$ mvn liquibase:update -Dliquibase.changesToApply=1
@@ -258,9 +258,9 @@
Upstream deside use three field to identify changeset:
- * each changeset mandatory marked by pair of ``user:id`` (which is actually any
- non-whitespace characters)
- * full path to file with changeset
+* each changeset mandatory marked by pair of ``user:id`` (which is actually any
+ non-whitespace characters)
+* full path to file with changeset
``user:id`` is actually any non-whitespace and non-colon text with
non-whitespace text. Upstream suggest to use changeset authro identity for
@@ -271,9 +271,9 @@
Reason to capture full path as part of identifier is very dumb. Upstream
arguments:
- * http://forum.liquibase.org/topic/why-does-the-change-log-contain-the-file-name
- * http://forum.liquibase.org/topic/i-need-to-ignore-the-filename-in-the-processing-to-see-if-a-change-set-has-already-been-applied
- * http://forum.liquibase.org/topic/logical-filepath-in-change-sets-and-changelog
+* http://forum.liquibase.org/topic/why-does-the-change-log-contain-the-file-name
+* http://forum.liquibase.org/topic/i-need-to-ignore-the-filename-in-the-processing-to-see-if-a-change-set-has-already-been-applied
+* http://forum.liquibase.org/topic/logical-filepath-in-change-sets-and-changelog
is very Java centric and require sticking to fixed changeset file location in
``CLASSPATH``.
@@ -332,9 +332,9 @@
..
- * http://stackoverflow.com/questions/19896436/how-to-configure-liquibase-not-to-include-file-path-or-name-for-calculating-chec
- * http://stackoverflow.com/questions/19959755/liquibase-how-to-disable-filename-column-check
- * http://stackoverflow.com/questions/18767815/refactoring-liquibase-changelog-files
+* http://stackoverflow.com/questions/19896436/how-to-configure-liquibase-not-to-include-file-path-or-name-for-calculating-chec
+* http://stackoverflow.com/questions/19959755/liquibase-how-to-disable-filename-column-check
+* http://stackoverflow.com/questions/18767815/refactoring-liquibase-changelog-files
Consult
``liquibase-core/src/main/java/liquibase/parser/core/formattedsql/FormattedSqlChangeLogParser.java``
@@ -400,23 +400,23 @@
wrong update that doesn't prepare data to constraint it shouldn't be commited
but rewritten.
- * http://blog.mgm-tp.com/2010/11/data-modeling-part2/
+* http://blog.mgm-tp.com/2010/11/data-modeling-part2/
Labels vs Contexts.
===================
- * http://forum.liquibase.org/topic/labels-vs-contexts-in-3-3-0
- * http://www.liquibase.org/2014/11/contexts-vs-labels.html
+* http://forum.liquibase.org/topic/labels-vs-contexts-in-3-3-0
+* http://www.liquibase.org/2014/11/contexts-vs-labels.html
How to apply LiquiBase to you DB?
=================================
- * http://www.liquibase.org/2015/07/executing-liquibase.html
+* http://www.liquibase.org/2015/07/executing-liquibase.html
Comparison LiquiBase with Python Django South and Ruby ActiveRecord.
====================================================================
- * http://south.readthedocs.org/en/latest/index.html
- * https://code.djangoproject.com/wiki/SchemaEvolution
- * http://guides.rubyonrails.org/active_record_basics.html
+* http://south.readthedocs.org/en/latest/index.html
+* https://code.djangoproject.com/wiki/SchemaEvolution
+* http://guides.rubyonrails.org/active_record_basics.html