Merge remote-tracking branch 'origin/master'

nvoxland · nvoxland · commit 515f73e7f3d2 · 2015-06-24T15:30:02.000-05:00
diff --git a/_includes/subnav_documentation.md b/_includes/subnav_documentation.md
@@ -12,4 +12,5 @@
 <li><a href="{{pageRoot}}/documentation/generating_changelogs.html"><span>Generate Changelog</span></a></li>
 <li><a href="{{pageRoot}}/documentation/dbdoc.html"><span>DBDoc</span></a></li>
 <li><a href="{{pageRoot}}/documentation/sql_output.html"><span>SQL Output</span></a></li>
-<li><a href="{{pageRoot}}/documentation/sdk/index.html"><span>SDK</span></a></li>
+<li><a href="{{pageRoot}}/documentation/sdk/index.html"><span>SDK</span></a></li>
+<li><a href="{{pageRoot}}/documentation/offline.html"><span>Offline Database Support</span></a></li>
diff --git a/documentation/command_line.md b/documentation/command_line.md
@@ -74,6 +74,7 @@ If you run the command line migrator without any arguments, you will get a help
 <table>
 <tr><th>Command</th><th>Description</th></tr>
 <tr><td>tag &lt;tag&gt;</td><td>"Tags" the current database state for future rollback.</td></tr>
+<tr><td>tagExists &lt;tag&gt;</td><td>Checks whether the given tag is already existing.</td></tr>
 <tr><td>status</td><td>Outputs count (list if --verbose) of unrun change sets.</td></tr>
 <tr><td>validate</td><td>Checks the changelog for errors.</td></tr>
 <tr><td>changelogSync</td><td>Mark all changes as executed in the database.</td></tr>
diff --git a/documentation/index.md b/documentation/index.md
@@ -46,6 +46,7 @@ includeDaticalBox: true
 <li><a href="spring.html">Spring</a></li>
 <li><a href="servlet_listener.html">Servlet Listener</a></li>
 <li><a href="cdi.html">CDI Environment</a></li>
+<li><a href="offline.html">Using Offline Database Support</a></li>
 </ul>
 
 <h2>Internals</h2>
@@ -93,4 +94,4 @@ If no context is specified, the changeset will run regardless of the execution c
 
 </div>
 
-</div>
+</div>
diff --git a/documentation/offline.md b/documentation/offline.md
@@ -26,7 +26,7 @@ _Since 3.1.0_
 
 If your environment does not lend itself to using updateSql with test and backup databases, you can run Liquibase using an "offline" database.
 
-Running in offline mode only supports "updateSql". It does not support direct update, diff, or preconditions as there is nothing to actually update or state to check.
+Running in offline mode only supports "updateSql", "rollbackSQL", "tag", and "tagExists". It does not support direct update, diff, or preconditions as there is nothing to actually update or state to check.
 
 An offline database is "connected" to using a url syntax of `offline:DATABASE_TYPE?param1=value1&aparam2=value2`.
 
@@ -42,5 +42,5 @@ An offline database is "connected" to using a url syntax of `offline:DATABASE_TY
 ### Examples:
 
 - `offline:oracle`
-- `offine:mssql?changeLogFile=/src/changelog.csv`
-- `offline:mysql?version=5.4.21&changeLogFile=/src/changelog.csv`
+- `offline:mssql?changeLogFile=/src/changelog.csv`
+- `offline:mysql?version=5.4.21&changeLogFile=/src/changelog.csv`
