blog-examples/liquibase
1
0
Fork 0
mirror of https://github.com/Example-uPagge/liquibase.git synced 2024-06-14 12:22:25 +03:00
Code Issues Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
Struchkov Mark 2022-04-24 01:30:18 +03:00
parent 3f1a6dc23c
commit 6ef4417e9b
77 changed files with 5660 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

83
.gitignore-back Normal file
View File

@ -0,0 +1,83 @@
HELP.md
target/
!.mvn/wrapper/maven-wrapper.jar
!**/src/main/**/target/
!**/src/test/**/target/
### STS ###
.apt_generated
.classpath
.factorypath
.project
.settings
.springBeans
.sts4-cache
### IntelliJ IDEA ###
.idea
*.iws
*.iml
*.ipr
### NetBeans ###
/nbproject/private/
/nbbuild/
/dist/
/nbdist/
/.nb-gradle/
build/
!**/src/main/**/build/
!**/src/test/**/build/
### VS Code ###
.vscode/
target/
pom.xml.tag
pom.xml.releaseBackup
pom.xml.versionsBackup
pom.xml.next
release.properties
dependency-reduced-pom.xml
buildNumber.properties
.mvn/timing.properties
.mvn/wrapper/maven-wrapper.jar
*.class
*.log
*.ctxt
.mtj.tmp/
*.jar
*.war
*.nar
*.ear
*.zip
*.tar.gz
*.rar
hs_err_pid*
.idea/**/workspace.xml
.idea/**/tasks.xml
.idea/**/usage.statistics.xml
.idea/**/dictionaries
.idea/**/shelf
.idea/**/contentModel.xml
.idea/**/dataSources/
.idea/**/dataSources.ids
.idea/**/dataSources.local.xml
.idea/**/sqlDataSources.xml
.idea/**/dynamic.xml
.idea/**/uiDesigner.xml
.idea/**/dbnavigator.xml
.idea/**/gradle.xml
.idea/**/libraries
cmake-build-*/
.idea/**/mongoSettings.xml
*.iws
out/
.idea_modules/
atlassian-ide-plugin.xml
.idea/replstate.xml
com_crashlytics_export_strings.xml
crashlytics.properties
crashlytics-build.properties
fabric.properties
.idea/httpRequests
.idea/caches/build_file_checksums.ser

10
.gitignore-tree Normal file
View File

@ -0,0 +1,10 @@
src
liquibase-4.9.1/*.txt
liquibase-4.9.1/examples
liquibase-4.9.1/licenses
liquibase-4.9.1/lib/liquibase_autocomplete.sh
liquibase-4.9.1/lib/liquibase_autocomplete_mac.bash
liquibase.iml
mvnw
mvnw.cmd
pom.xml

5
README.md Normal file
View File

@ -0,0 +1,5 @@
# Liquibase Example
Это демо проект для моей статье об использовании Liquibase в качестве системы миграции БД.
https://struchkov.dev/blog/get-started-liquibase

3
docker.sh Normal file
View File

@ -0,0 +1,3 @@
#!/bin/sh
docker run --name liquibase --network host -v YOUR_PATH_TO_db/changelog:/liquibase/db/changelog liquibase/liquibase:4.9.1 --defaultsFile=/liquibase/db/changelog/liquibase.properties update
docker rm liquibase

1
liquibase-4.9.1/ABOUT.txt Normal file
View File

@ -0,0 +1 @@
LIQUIBASE is a registered trademark of Liquibase.

258
liquibase-4.9.1/GETTING_STARTED.txt Normal file
View File

@ -0,0 +1,258 @@
Liquibase Version 4.9.1
Getting Started
--------------------------------------------
Thanks for downloading and installing Liquibase 4.9.1 from Liquibase.
By using the installer, you already have all the dependencies, directories, config,
and properties files to get started exploring the Liquibase examples provided, which
is a great way to understand the core concepts with a direct command-line introductory
experience.
Adding Liquibase to Your Path
--------------------------------------------
If you do not want always to provide an absolute path to the liquibase command,
add `/path/to/installed/liquibase` to your PATH. If you selected this option
during the installation process, this should have been done for you.
EXAMPLE PROJECTS
--------------------------------------------
This installation contains an "examples" directory, which includes everything
required to use Liquibase against a sample in-memory database.
There are two projects under the examples directory:
* "examples/sql" directory shows how to use a SQL formatted changelog
* "examples/xml" directory shows how to use an XML formatted changelog
Both projects utilize the same setup & examples and only differ in the changelog type.
Setting Up Your Workspace
-------------------------
Copy the "examples" directory to another location on your machine.
* Installed location: "<chosen_install_dir>/liquibase/examples"
* Example new location: "<USER_HOME>/apps/liquibase-projects/examples"
What got copied?
In both ".../examples/sql" and "example/xml" there is a liquibase.properties file,
which provides default values that allow you to run command-line (CLI) commands
immediately with Liquibase. This file is pre-configured to point to the changelog
you copied and the `start-h2` developer database.
In both ".../examples/sql" and "example/xml" there is a sample changelogfile.
While not required, it is a best practice to keep your changelogs in a unique and
descriptive directory structure. Changelogs are normally stored in your version
control system along with your application code and match the directory structures
you use there.
Configuring your liquibase.properties file
--------------------------------------------
*** NOTE: You do not need to change any settings to be able to run liquibase examples ***
In your command line or Terminal app, navigate to the sql or xml sub-directory in
the example directory to examine your pre-configured liquibase.properties files.
The liquibase.properties file stores properties which rarely change, such as
database connection information. Properties stored here save time and reduce the
risk of mistyped command line arguments. Any parameter that could be specified on
the command line can also be specified in the properties file. If a parameter is
specified in both the properties file and the command line, the command line value
will override the value in the file.
Learn more: https://www.liquibase.org/documentation/config_properties.html
Starting the Example H2 Database
--------------------------------------------
USING H2
H2 is a standard SQL database and can be used to simulate working in a more
complex database.
To start the example database:
* open your command line or Terminal app
* navigate to the directory where you placed "examples" directory
* run `examples/start-h2`.
To stop the example database:
* run `ctrl-c' in the terminal running examples/start-h2
Notes
Running `examples/start-h2` starts local H2 databases that listen on port 9090, and
it opens a browser to the database console on the same port.
* The Example h2 databases do not store data and will reset when the start-h2
process ends via "ctrl-c".
The start-h2 script starts two databases:
1. A Developer Database: Corresponds to what you may use as a local database.
2. An Integration Database: Corresponds to another database in your pipeline.
About the console:
* The web-based console allows you to see all objects in your database in the
left navigation and run SQL statements on the right side.
* Along the top is a toolbar that includes a Refresh button which can be used
to reload the left-side object view if changes are made to your database
outside of the console (like with Liquibase).
* The Integration database can be viewed with the link provided to you from
the Developer database browser. You can also see which database you are
connected to by looking at the URL at the top of the object view.
* As a test, try entering `create table test_table (id int)` in the text area
and hit "Run". After, you should see "TEST_TABLE" appear in the object view.
NOTE: If you run formatted SQL or XML on the H2 database, and then want to attempt
using the other method, you must restart the H2 database before running it again
or you will receive an update failure due to objects already existing on the database.
Running Your First Update
-------------------------
The main Liquibase command you will use is "update", which applies any changes not
yet run in your changelog to your database.
First,
1. Open a different command-line or Terminal app.
2. Navigate to your ...examples/sql directory (or xml)
To run the update command:
1. In your command prompt run: `liquibase update`
You should see a message saying: "Update has been successful."
2. Refresh your developer database console page.
You should now see the following tables added to the object view:
- COMPANY
- DATABASECHANGELOG
- DATABASECHANGELOGLOCK
- PERSON
By running `liquibase update`, your database now matches the desired database state
as defined by the changelog script.
The DATABASECHANGELOG and DATABASECHANGELOGLOCK tables are liquibase-metadata tables.
Also, the changelog created the COMPANY and PERSON tables.
Now, open the sample.changelog.xml or samplechangelog.h2.sql file in your favorite
text editor.
In each file, you can see how changes were defined as a series of changeSets. Each
changeSet is uniquely identified by the "id" and "author" fields. Liquibase uses
these fields to track what changes have been run and what has not.
When you ran the "update" command, Liquibase evaluated which changeSets had not
been run against your target database, then ran them.
Adding New ChangeSets
---------------------
Running the update command allowed your developer database to match the defined
state. Now that they match, you can start adding additional changes you need. If
you have not run your first update, please follow the instructions in the previous
section before completing this section.
In this example, we will add a new changeSet to create a "works for" column in the
persons table with a foreign key to the company table.
To add this changeSet, open the sample changelog file in your existing editor, and
copy + paste one of the following changeSet examples:
XML changelog example code
---------------------------
<changeSet id="4" author="your.name">
<addColumn tableName="person">
<column name="worksfor_company_id" type="int"/>
</addColumn>
</changeSet>
<changeSet id="5" author="your.name">
<addForeignKeyConstraint
constraintName="fk_person_worksfor"
baseTableName="person"
baseColumnNames="worksfor_company_id"
referencedTableName="company"
referencedColumnNames="id"/>
</changeSet>
SQL changelog example code
---------------------------
--changeset your.name:4
ALTER TABLE person ADD worksfor_company_id INT;
--changeset your.name:5
ALTER TABLE person ADD CONSTRAINT fk_person_worksfor FOREIGN KEY (worksfor_company_id) REFERENCES company(id);
NOTE: It's best practice to wrap every statement in its own changeSet block.
Now, run `liquibase update` again & refresh your database console.
You will see the new column on the person table and the new constraint.
NOTE: If you run formatted SQL or XML on the H2 database, then want to attempt using
the other method, you must restart the H2 database before running it again or you
will receive an update failure due to objects already existing on the database.
Promoting Changes
-----------------
Now that we added a new changeSet and the database structure is what we want, we
are ready to apply those changes to our integration database.
At this time in the workflow, you should commit your changelog to version control
and/or build an artifact containing it. However, for this tutorial, we will run
it directly against our other database.
To apply the changes to the integration database run:
`liquibase --url=jdbc:h2:tcp://localhost:9090/mem:integration update`
By passing the --url parameter, you override the URL value specified in the
liquibase.properties file, but still use all the other parameters in the file.
After running "update" against the integration database, you should now see the
COMPANY and PERSON tables in your integration web console.
Standard Development Workflow
-----------------------------
For more information on the Standard Development Workflow you just completed, see:
https://www.liquibase.org/documentation/workflows/lb-developer-workflow.html
Next Steps
----------
Now that you have a feel for Liquibase against your sample database, you can try
it against your standard databases.
Just add your database's jdbc drivers to the "lib" directory in the Liquibase
install directory and update the URL, username, and password in the
liquibase.properties file.
Also, check the documentation associated with your specific database to locate
the correct url format and download the driver jar. Then use the Standard
Development Workflow to make changes against your database.
Help & Support
----------------------------------------
For questions regarding Liquibase, you can submit an email to support@liquibase.org
or submit a post on stack overflow and use the #liquibase tag here:
https://stackoverflow.com/questions/tagged/liquibase
You can also post questions to these Liquibase forums:
Liquibase User Forum: https://forum.liquibase.org/#Forum/liquibase-users
Liquibase Developer Forum: https://forum.liquibase.org/#Forum/liquibase-development.
Liquibase Documentation: www.liquibase.org/documentation/index.html
Need Liquibase Support? Get customer support by upgrading to Liquibase Pro here:
https://support.liquibase.org/
Copyright 2021 Liquibase, Inc. All rights reserved. The program is subject to the
license agreement, copyright, trademark, patent, and other laws.

202
liquibase-4.9.1/LICENSE.txt Normal file
View File

@ -0,0 +1,202 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

81
liquibase-4.9.1/README.txt Normal file
View File

@ -0,0 +1,81 @@
Liquibase Version 4.9.1
Introduction
--------------------------------------------
Thanks for downloading and installing Liquibase 4.9.1 from Liquibase.
By using the installer, you already have all the dependencies, directories, config,
and properties files to get started exploring the Liquibase examples provided.
This is a great way to understand the core concepts with direct command-line experience.
What was Installed
--------------------------------------------
The default install location on Windows is "\Program Files\liquibase"
The default install location on Mac is "/usr/local/opt/liquibase"
The following software was installed:
* Liquibase ( http://liquibase.org )
* H2 Database ( https://www.h2database.com )
* AdoptOpenJDK 13 ( https://adoptopenjdk.net )
This installer creates the following directories:
* liquibase/lib
* liquibase/licenses
* liquibase/jre
* liquibase/examples/sql
* liquibase/examples/xml
**NOTE: JRE Install location for mac users is: liquibase/.install4j/jre.bundle/Contents/Home/bin/java**
Files are:
* liquibase/ABOUT.txt
* liquibase/LICENSE.txt
* liquibase/liquibase.sh
* liquibase/liquibase.bat
* liquibase/liquibase.jar
* liquibase/README.txt
* liquibase/GETTING_STARTED.txt
* liquibase/examples/start-h2
* liquibase/examples/start-h2.bat
H2 Database Program
----------------------------------------
As Liquibase ships with an h2 database example, the h2 jdbc driver was placed into
your chosen installation directory.
For information on using and configuring the h2 database see:
https://www.liquibase.org/documentation/tutorials/h2.html
Open JDK
----------------------------------------
We placed AdoptOpenJDK ( https://adoptopenjdk.net ) in your chosen installation
directory.
All AdoptOpenJDK binaries and scripts are open-source licensed and available for
free. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or
its affiliates. Other names may be trademarks of their respective owners.
Help & Support
----------------------------------------
For questions regarding Liquibase, you can submit an email to support@liquibase.org
or submit a post on stack overflow and use the #liquibase tag:
https://stackoverflow.com/questions/tagged/liquibase
You can also post questions to these Liquibase forums:
Liquibase User Forum: https://forum.liquibase.org/#Forum/liquibase-users
Liquibase Developer Forum: https://forum.liquibase.org/#Forum/liquibase-development
Liquibase Documentation: http://liquibase.org/documentation
Need Liquibase Support? Get customer support by upgrading to Liquibase Pro here: https://support.liquibase.org
----------------------------------------
The program is subject to the license agreement, copyright, trademark, patent, and other laws.
Copyright 2021 Liquibase, Inc. All rights reserved.

17
liquibase-4.9.1/UNINSTALL.txt Normal file
View File

@ -0,0 +1,17 @@
Uninstalling Liquibase
--------------------------------------------
To uninstall Liquibase, delete the directory where it was installed.
If you used the installer you can also use the uninstall.exe (Windows) or Liquibase Uninstaller (Mac) to remove these files.
Help & Support
----------------------------------------
For questions regarding Liquibase, you can submit an email to answers@liquibase.org or submit a post on stack overflow and use the #liquibase tag: https://stackoverflow.com/questions/tagged/liquibase
You can also post questions to these Liquibase forums:
Liquibase User Forum: https://forum.liquibase.org/#Forum/liquibase-users
Liquibase Developer Forum: https://forum.liquibase.org/#Forum/liquibase-development.
Liquibase Documentation: http://liquibase.org/documentation
Need Liquibase Support? Get customer support by upgrading to Liquibase Pro here: https://support.liquibase.org/

2406
liquibase-4.9.1/changelog.txt Normal file
View File

File diff suppressed because it is too large Load Diff

10
liquibase-4.9.1/db/changelog/db.changelog-master.xml Normal file
View File

@ -0,0 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<include file="v.1.0.0/cumulative-changelog.xml" relativeToChangelogFile="true"/>
<include file="v.2.0.0/cumulative-changelog.xml" relativeToChangelogFile="true"/>
</databaseChangeLog>

5
liquibase-4.9.1/db/changelog/liquibase.properties Normal file
View File

@ -0,0 +1,5 @@
url=jdbc:postgresql://localhost:5432/liquibase_example
username=postgres
password=
changeLogFile=db/changelog/db.changelog-master.xml
liquibase.hub.mode=off

34
liquibase-4.9.1/db/changelog/v.1.0.0/create-table.xml Normal file
View File

@ -0,0 +1,34 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="create-table-person" author="uPagge">
<createTable tableName="person">
<column name="id" type="int" autoIncrement="true">
<constraints nullable="false" primaryKey="true"/>
</column>
<column name="first_name" type="varchar(64)"/>
</createTable>
</changeSet>
<changeSet id="add-new-column-address" author="uPagge">
<addColumn tableName="person">
<column name="address" type="varchar(300)"/>
</addColumn>
</changeSet>
<changeSet id="create-table-book" author="uPagge">
<createTable tableName="book">
<column name="id" type="int" autoIncrement="true">
<constraints nullable="false" primaryKey="true"/>
</column>
<column name="name" type="varchar(64)"/>
<column name="author_id" type="int">
<constraints foreignKeyName="book_author_id_person_id" references="person(id)"/>
</column>
</createTable>
</changeSet>
</databaseChangeLog>

13
liquibase-4.9.1/db/changelog/v.1.0.0/cumulative-changelog.xml Normal file
View File

@ -0,0 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="add-tag-1.0.0" author="uPagge">
<tagDatabase tag="v.1.0.0"/>
</changeSet>
<include file="create-table.xml" relativeToChangelogFile="true"/>
</databaseChangeLog>

54
liquibase-4.9.1/db/changelog/v.2.0.0/create-table-hero.xml Normal file
View File

@ -0,0 +1,54 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="create-table-hero" author="uPagge">
<createTable tableName="hero">
<column name="id" type="int" autoIncrement="true">
<constraints nullable="false" primaryKey="true"/>
</column>
<column name="book_id" type="int">
<constraints nullable="false"/>
</column>
<column name="name" type="varchar(64)">
<constraints nullable="false"/>
</column>
</createTable>
</changeSet>
<changeSet id="create-fk" author="uPagge">
<addForeignKeyConstraint baseTableName="hero" baseColumnNames="book_id"
constraintName="hero_book_id"
referencedTableName="book" referencedColumnNames="id"
deleteCascade="true"/>
</changeSet>
<changeSet id="insert-into" author="uPagge">
<insert tableName="person">
<column name="first_name" value="Александр"/>
</insert>
<insert tableName="book">
<column name="name" value="Капитанская дочка"/>
<column name="author_id" value="1"/>
</insert>
<insert tableName="hero">
<column name="name" value="Савельич"/>
<column name="book_id" value="1"/>
</insert>
<rollback>
<delete tableName="hero">
<where>name = 'Савельич'</where>
</delete>
<delete tableName="book">
<where>name = 'Капитанская дочка'</where>
</delete>
<delete tableName="person">
<where>first_name = 'Александр'</where>
</delete>
</rollback>
</changeSet>
</databaseChangeLog>

13
liquibase-4.9.1/db/changelog/v.2.0.0/cumulative-changelog.xml Normal file
View File

@ -0,0 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="add-tag-2.0.0" author="uPagge">
<tagDatabase tag="v.2.0.0"/>
</changeSet>
<include file="create-table-hero.xml" relativeToChangelogFile="true"/>
</databaseChangeLog>

18
liquibase-4.9.1/examples/json/blank-changelog.json Normal file
View File

@ -0,0 +1,18 @@
{ "databaseChangeLog": [
"changeset": {
"id": "1",
"author": "your.name",
"changes": [
{
}
]
},
"changeset": {
"id": "2",
"author": "your.name",
"changes": [
{
}
]
}
]}

135
liquibase-4.9.1/examples/json/example-changelog.json Normal file
View File

@ -0,0 +1,135 @@
{ "databaseChangeLog": [
{
"changeSet": {
"id": "1",
"author": "your.name",
"labels": "example-label",
"context": "example-context",
"comment": "example-comment",
"changes": [
{
"createTable": {
"tableName": "person",
"columns": [
{
"column": {
"name": "id",
"type": "int",
"autoIncrement": true,
"constraints": {
"primarykey": true,
"nullable": false
}
}
},
{
"column": {
"name": "name",
"type": "varchar(50)",
"constraints": {
"nullable": false
}
}
},
{
"column": {
"name": "addresss1",
"type": "varchar(50)"
}
},
{
"column": {
"name": "addresss2",
"type": "varchar(50)"
}
},
{
"column": {
"name": "city",
"type": "varchar(30)"
}
}
]
}
}]
}
},
{
"changeSet": {
"id": "2",
"author": "your.name",
"labels": "example-label",
"context": "example-context",
"comment": "example-comment",
"changes": [
{
"createTable": {
"tableName": "company",
"columns": [
{
"column": {
"name": "id",
"type": "int",
"autoIncrement": true,
"constraints": {
"primarykey": true,
"nullable": false
}
}
},
{
"column": {
"name": "name",
"type": "varchar(50)",
"constraints": {
"nullable": false
}
}
},
{
"column": {
"name": "addresss1",
"type": "varchar(50)"
}
},
{
"column": {
"name": "addresss2",
"type": "varchar(50)"
}
},
{
"column": {
"name": "city",
"type": "varchar(30)"
}
}
]
}
}]
}
},
{
"changeSet": {
"id": "3",
"author": "other.dev",
"labels": "example-label",
"context": "example-context",
"comment": "example-comment",
"changes": [
{
"addColumn": {
"tableName": "person",
"columns": [
{
"column": {
"name": "country",
"type": "varchar(2)"
}
}
]
}
}]
}
}
]}

30
liquibase-4.9.1/examples/json/example-changeset-json.txt Normal file
View File

@ -0,0 +1,30 @@
"changeSet": {
"id": "1",
"author": "dev",
"changes": [
{
"createTable": {
"tableName": "person",
"columns": [
{
"column": {
"name": "id",
"type": "int",
"autoIncrement": true,
"constraints": {
"primaryKey": true,
"nullable": false
}
}
},
{
"column": {
"name": "name",
"type": "varchar(255)"
}
}
]
}
}
]
}

76
liquibase-4.9.1/examples/json/liquibase.properties Normal file
View File

@ -0,0 +1,76 @@
#### _ _ _ _
## | | (_) (_) |
## | | _ __ _ _ _ _| |__ __ _ ___ ___
## | | | |/ _` | | | | | '_ \ / _` / __|/ _ \
## | |___| | (_| | |_| | | |_) | (_| \__ \ __/
## \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|
## | |
## |_|
##
## The liquibase.properties file stores properties which do not change often,
## such as database connection information. Properties stored here save time
## and reduce risk of mistyped command line arguments.
## Learn more: https://www.liquibase.org/documentation/config_properties.html
####
####
## Note about relative and absolute paths:
## The liquibase.properties file requires paths for some properties.
## The classpath is the path/to/resources (ex. src/main/resources).
## The changeLogFile path is relative to the classpath.
## The url H2 example below is relative to 'pwd' resource.
####
# Enter the path for your changelog file.
changeLogFile=example-changelog.json
#### Enter the Target database 'url' information ####
liquibase.command.url=jdbc:h2:tcp://localhost:9090/mem:dev
# Enter the username for your Target database.
liquibase.command.username: dbuser
# Enter the password for your Target database.
liquibase.command.password: letmein
#### Enter the Source Database 'referenceUrl' information ####
## The source database is the baseline or reference against which your target database is compared for diff/diffchangelog commands.
# Enter URL for the source database
liquibase.command.referenceUrl: jdbc:h2:tcp://localhost:9090/mem:integration
# Enter the username for your source database
liquibase.command.referenceUsername: dbuser
# Enter the password for your source database
liquibase.command.referencePassword: letmein
# Logging Configuration
# logLevel controls the amount of logging information generated. If not set, the default logLevel is INFO.
# Valid values, from least amount of logging to most, are:
# OFF, ERROR, WARN, INFO, DEBUG, TRACE, ALL
# If you are having problems, setting the logLevel to DEBUG and re-running the command can be helpful.
# logLevel: DEBUG
# The logFile property controls where logging messages are sent. If this is not set, then logging messages are
# displayed on the console. If this is set, then messages will be sent to a file with the given name.
# logFile: liquibase.log
#### Liquibase Pro Key Information ####
# Learn more, contact support, or get or renew a Pro Key at https://www.liquibase.com/protrial
# liquibase.pro.licensekey:
#### Liquibase Hub Information ####
# Liquibase Hub is a free secure SaaS portal providing status reporting, monitoring & insights
# into your Liquibase database release automation.
# https://hub.liquibase.com
## Add your free Hub API key here
# liquibase.hub.apikey:
# liquibase.hub.mode:all
## Get documentation at docs.liquibase.com ##
## Get certified courses at learn.liquibase.com ##
## Get support at liquibase.com/support ##

12
liquibase-4.9.1/examples/sql/blank-changelog.sql Normal file
View File

@ -0,0 +1,12 @@
--liquibase formatted sql
/* https://www.liquibase.org/documentation/sql_format.html */
--changeset authorname:1
/* Insert SQL change objects here */
--changeset authorname:2
/* Insert SQL change objects here */

29
liquibase-4.9.1/examples/sql/example-changelog.sql Normal file
View File

@ -0,0 +1,29 @@
--liquibase formatted sql
--changeset your.name:1 labels:example-label context:example-context
--comment: example comment
create table person (
id int primary key auto_increment not null,
name varchar(50) not null,
address1 varchar(50),
address2 varchar(50),
city varchar(30)
)
--rollback DROP TABLE person;
--changeset your.name:2 labels:example-label context:example-context
--comment: example comment
create table company (
id int primary key auto_increment not null,
name varchar(50) not null,
address1 varchar(50),
address2 varchar(50),
city varchar(30)
)
--rollback DROP TABLE company;
--changeset other.dev:3 labels:example-label context:example-context
--comment: example comment
alter table person add column country varchar(2)
--rollback ALTER TABLE person DROP COLUMN country;

7
liquibase-4.9.1/examples/sql/example-changeset-sql.txt Normal file
View File

@ -0,0 +1,7 @@
(example-changeset-sql.txt)
--changeset dev:1
create table test1(
id int primary key,
name varchar(255)
);

76
liquibase-4.9.1/examples/sql/liquibase.properties Normal file
View File

@ -0,0 +1,76 @@
#### _ _ _ _
## | | (_) (_) |
## | | _ __ _ _ _ _| |__ __ _ ___ ___
## | | | |/ _` | | | | | '_ \ / _` / __|/ _ \
## | |___| | (_| | |_| | | |_) | (_| \__ \ __/
## \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|
## | |
## |_|
##
## The liquibase.properties file stores properties which do not change often,
## such as database connection information. Properties stored here save time
## and reduce risk of mistyped command line arguments.
## Learn more: https://www.liquibase.org/documentation/config_properties.html
####
####
## Note about relative and absolute paths:
## The liquibase.properties file requires paths for some properties.
## The classpath is the path/to/resources (ex. src/main/resources).
## The changeLogFile path is relative to the classpath.
## The url H2 example below is relative to 'pwd' resource.
####
# Enter the path for your changelog file.
changeLogFile=example-changelog.sql
#### Enter the Target database 'url' information ####
liquibase.command.url=jdbc:h2:tcp://localhost:9090/mem:dev
# Enter the username for your Target database.
liquibase.command.username: dbuser
# Enter the password for your Target database.
liquibase.command.password: letmein
#### Enter the Source Database 'referenceUrl' information ####
## The source database is the baseline or reference against which your target database is compared for diff/diffchangelog commands.
# Enter URL for the source database
liquibase.command.referenceUrl: jdbc:h2:tcp://localhost:9090/mem:integration
# Enter the username for your source database
liquibase.command.referenceUsername: dbuser
# Enter the password for your source database
liquibase.command.referencePassword: letmein
# Logging Configuration
# logLevel controls the amount of logging information generated. If not set, the default logLevel is INFO.
# Valid values, from least amount of logging to most, are:
# OFF, ERROR, WARN, INFO, DEBUG, TRACE, ALL
# If you are having problems, setting the logLevel to DEBUG and re-running the command can be helpful.
# logLevel: DEBUG
# The logFile property controls where logging messages are sent. If this is not set, then logging messages are
# displayed on the console. If this is set, then messages will be sent to a file with the given name.
# logFile: liquibase.log
#### Liquibase Pro Key Information ####
# Learn more, contact support, or get or renew a Pro Key at https://www.liquibase.com/protrial
# liquibase.pro.licensekey:
#### Liquibase Hub Information ####
# Liquibase Hub is a free secure SaaS portal providing status reporting, monitoring & insights
# into your Liquibase database release automation.
# https://hub.liquibase.com
## Add your free Hub API key here
# liquibase.hub.apikey:
# liquibase.hub.mode:all
## Get documentation at docs.liquibase.com ##
## Get certified courses at learn.liquibase.com ##
## Get support at liquibase.com/support ##

55
liquibase-4.9.1/examples/sql/liquibase.sqlcmd.conf Normal file
View File

@ -0,0 +1,55 @@
#### _ _ _ _ _____
## | | (_) (_) | | __ \
## | | _ __ _ _ _ _| |__ __ _ ___ ___ | |__) | __ ___
## | | | |/ _` | | | | | '_ \ / _` / __|/ _ \ | ___/ '__/ _ \
## | |___| | (_| | |_| | | |_) | (_| \__ \ __/ | | | | | (_) |
## \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___| |_| |_| \___/
## | |
## |_|
##
## The liquibase.sqlcmd.conf file stores properties which are used during the
## execution of the Microsoft SQLCMD tool.
## Learn more: https://www.liquibase.org/documentation/config_properties.html
####
####
## Note about relative and absolute paths:
## The liquibase.sqlcmd.path must be a valid path to the SQLCMD executable.
## The liquibase.sqlcmd.timeout value can be one of:
## -1 - disable the timeout
## Any integer value > 0 (measured in seconds)
##
####
# The full path to the SQLCMD executable.
# Sample Linux path
# liquibase.sqlcmd.path=/opt/mssql-tools/bin/sqlcmd
# Sample Windows path
# liquibase.sqlcmd.path="C:\\Program Files\\Microsoft SQL Server\\Client SDK\\ODBC\\170\\Tools\\Binn\\SQLCMD.EXE"
# A valid timeout value for the execution of the SQLCMD tool
liquibase.sqlcmd.timeout=-1
# Flag to indicate whether or not to keep the temporary SQL file after execution of SQLCMD.
# True = keep False = delete (default)
liquibase.sqlcmd.keep.temp=true
# OPTIONAL Flag to designate the location to store temporary SQL file after execution of SQLCMD.
# Liquibase will attempt to use path exactly as entered, so please ensure it complies with your OS requirements.
# liquibase.sqlcmd.keep.temp.path=
# OPTIONAL Flag to designate the name of temporary SQL file after execution of SQLCMD.
# Liquibase will attempt to use the name exactly as entered, so please ensure it complies with your OS requirements.
# liquibase.sqlcmd.keep.temp.name=
# OPTIONAL Args to pass directly to SQLCMD.
# Learn about SQLCMD args at https://<link>
# Note: The delimiter for args is a space eg:" " and not "," or ";" separated.
# liquibase.sqlcmd.args=
# OPTIONAL Path to a log file for the SQLCMD output
# liquibase.sqlcmd.logFile=
#
# OPTIONAL Name of a custom executor to use instead of SQLCMD
# The Executor must be on the Liquibase classpath
# liquibase.sqlcmd.executor=

51
liquibase-4.9.1/examples/sql/liquibase.sqlplus.conf Normal file
View File

@ -0,0 +1,51 @@
#### _ _ _ _ _____
## | | (_) (_) | | __ \
## | | _ __ _ _ _ _| |__ __ _ ___ ___ | |__) | __ ___
## | | | |/ _` | | | | | '_ \ / _` / __|/ _ \ | ___/ '__/ _ \
## | |___| | (_| | |_| | | |_) | (_| \__ \ __/ | | | | | (_) |
## \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___| |_| |_| \___/
## | |
## |_|
##
## The liquibase.sqlplus.conf file stores properties which are used during the
## execution of the Oracle SQLPLUS tool.
## Learn more: https://www.liquibase.org/documentation/config_properties.html
####
####
## Note about relative and absolute paths:
## The liquibase.sqlplus.path must be a valid path to the SQLPlUS executable.
## The liquibase.sqlplus.timeout value can be one of:
## -1 - disable the timeout
## Any integer value > 0 (measured in seconds)
##
####
# The full path to the SQLPLUS executable.
# Sample Linux path
# liquibase.sqlplus.path=/apps/app/12.2.0.1.0/oracle/product/12.2.0.1.0/client_1/bin/sqlplus
# Sample Windows path
# liquibase.sqlplus.path=c:\\oracle\\product\\11.2.0\\client_1\\bin\\sqlplus.exe
# A valid timeout value for the execution of the SQLPLUS tool
liquibase.sqlplus.timeout=-1
# Flag to indicate whether or not to keep the temporary SQL file after execution of SQLPLUS.
# True = keep False = delete (default)
liquibase.sqlplus.keep.temp=true
# OPTIONAL Flag to designate the location to store temporary SQL file after execution of SQLPLUS.
# Liquibase will attempt to use path exactly as entered, so please ensure it complies with your OS requirements.
# liquibase.sqlplus.keep.temp.path=
# OPTIONAL Flag to designate the name of temporary SQL file after execution of SQLPLUS.
# Liquibase will attempt to use the name exactly as entered, so please ensure it complies with your OS requirements.
# liquibase.sqlplus.keep.temp.name=
# OPTIONAL Args to pass directly to SQLPLUS.
# Learn about SQLPLUS args at https://docs.oracle.com/cd/B10501_01/server.920/a90842/ch4.htm
# Note: The delimiter for args is a space eg:" " and not "," or ";" separated.
# liquibase.sqlplus.args=
# OPTIONAL Name of a custom executor to use instead of SQLPLUS
# The Executor must be on the Liquibase classpath
# liquibase.sqlplus.executor=

38
liquibase-4.9.1/examples/start-h2 Executable file
View File

@ -0,0 +1,38 @@
#!/usr/bin/env bash
if [ -z "${LIQUIBASE_HOME}" ]; then
#liquibase home is not set
LIQUIBASE_PATH="$(which liquibase)"
if [ -z "${LIQUIBASE_PATH}" ]; then
echo "Must set LIQUIBASE_HOME environment variable, or have liquibase in your PATH"
exit 1
fi
LIQUIBASE_HOME=$(dirname "$(which liquibase)")
fi
if [ -z "${JAVA_HOME}" ]; then
#JAVA_HOME not set, try to find a bundled version
if [ -d "${LIQUIBASE_HOME}/jre" ]; then
JAVA_HOME="$LIQUIBASE_HOME/jre"
elif [ -d "${LIQUIBASE_HOME}/.install4j/jre.bundle/Contents/Home" ]; then
JAVA_HOME="${LIQUIBASE_HOME}/.install4j/jre.bundle/Contents/Home"
fi
fi
if [ -z "${JAVA_HOME}" ]; then
JAVA_PATH="$(which java)"
if [ -z "${JAVA_PATH}" ]; then
echo "Cannot find java in your path. Install java or use the JAVA_HOME environment variable"
exit 1
fi
else
#Use path in JAVA_HOME
JAVA_PATH="${JAVA_HOME}/bin/java"
fi
"${JAVA_PATH}" -cp "${LIQUIBASE_HOME}/lib/h2-2.1.210.jar:${LIQUIBASE_HOME}/liquibase.jar" liquibase.example.StartH2Main

34
liquibase-4.9.1/examples/start-h2.bat Normal file
View File

@ -0,0 +1,34 @@
@echo off
if "%OS%" == "Windows_NT" setlocal
setlocal enabledelayedexpansion
rem %~dp0 is expanded pathname of the current script under NT
rem %~p0 is the directory of the current script
if exist %~p0\..\liquibase.jar SET LIQUIBASE_HOME="%~p0\.."
if "%LIQUIBASE_HOME%"=="" (
FOR /F "tokens=* USEBACKQ" %%g IN (`where liquibase.bat`) do (SET "LIQUIBASE_HOME=%%~dpg")
)
if "%LIQUIBASE_HOME%"=="" (
echo "Must set LIQUIBASE_HOME environment variable, or have liquibase.bat in your PATH"
exit /B 1
)
if "%JAVA_HOME%"=="" (
rem check for jre dir in liquibase_home
if NOT "%LIQUIBASE_HOME%"=="" if exist "%LIQUIBASE_HOME%\jre" (
set JAVA_HOME=%LIQUIBASE_HOME%\jre
)
)
if "%JAVA_HOME%"=="" (
set JAVA_PATH=java
) else (
set JAVA_PATH=%JAVA_HOME%\bin\java
)
"%JAVA_PATH%" -cp "%LIQUIBASE_HOME%\lib\h2-2.1.210.jar;%LIQUIBASE_HOME%\liquibase.jar" liquibase.example.StartH2Main

18
liquibase-4.9.1/examples/xml/blank-changelog.xml Normal file
View File

@ -0,0 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:pro="http://www.liquibase.org/xml/ns/pro"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd
http://www.liquibase.org/xml/ns/pro http://www.liquibase.org/xml/ns/pro/liquibase-pro-4.6.xsd ">
<changeSet id="1" author="author name">
<!--Insert XML change objects here https://www.liquibase.org/documentation/xml_format.html-->
</changeSet>
<changeSet id="2" author="author name">
<!--Insert XML change objects here https://www.liquibase.org/documentation/xml_format.html-->
</changeSet>
</databaseChangeLog>

46
liquibase-4.9.1/examples/xml/example-changelog.xml Normal file
View File

@ -0,0 +1,46 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:pro="http://www.liquibase.org/xml/ns/pro"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd
http://www.liquibase.org/xml/ns/pro http://www.liquibase.org/xml/ns/pro/liquibase-pro-4.6.xsd ">
<changeSet id="1" author="your.name" labels="example-label" context="example-context">
<comment>example-comment</comment>
<createTable tableName="person">
<column name="id" type="int" autoIncrement="true">
<constraints primaryKey="true" nullable="false"/>
</column>
<column name="name" type="varchar(50)">
<constraints nullable="false"/>
</column>
<column name="address1" type="varchar(50)"/>
<column name="address2" type="varchar(50)"/>
<column name="city" type="varchar(30)"/>
</createTable>
</changeSet>
<changeSet id="2" author="your.name" labels="example-label" context="example-context">
<comment>example-comment</comment>
<createTable tableName="company">
<column name="id" type="int" autoIncrement="true">
<constraints primaryKey="true" nullable="false"/>
</column>
<column name="name" type="varchar(50)">
<constraints nullable="false"/>
</column>
<column name="address1" type="varchar(50)"/>
<column name="address2" type="varchar(50)"/>
<column name="city" type="varchar(30)"/>
</createTable>
</changeSet>
<changeSet id="3" author="other.dev" labels="example-label" context="example-context">
<comment>example-comment</comment>
<addColumn tableName="person">
<column name="country" type="varchar(2)"/>
</addColumn>
</changeSet>
</databaseChangeLog>

13
liquibase-4.9.1/examples/xml/example-changeset-xml.txt Normal file
View File

@ -0,0 +1,13 @@
<changeSet id="1" author="your.name">
<createTable tableName="person">
<column name="id" type="int">
<constraints primaryKey="true"/>
</column>
<column name="name" type="varchar(50)">
<constraints nullable="false"/>
</column>
<column name="address1" type="varchar(50)"/>
<column name="address2" type="varchar(50)"/>
<column name="city" type="varchar(30)"/>
</createTable>
</changeSet>

76
liquibase-4.9.1/examples/xml/liquibase.properties Normal file
View File

@ -0,0 +1,76 @@
#### _ _ _ _
## | | (_) (_) |
## | | _ __ _ _ _ _| |__ __ _ ___ ___
## | | | |/ _` | | | | | '_ \ / _` / __|/ _ \
## | |___| | (_| | |_| | | |_) | (_| \__ \ __/
## \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|
## | |
## |_|
##
## The liquibase.properties file stores properties which do not change often,
## such as database connection information. Properties stored here save time
## and reduce risk of mistyped command line arguments.
## Learn more: https://www.liquibase.org/documentation/config_properties.html
####
####
## Note about relative and absolute paths:
## The liquibase.properties file requires paths for some properties.
## The classpath is the path/to/resources (ex. src/main/resources).
## The changeLogFile path is relative to the classpath.
## The url H2 example below is relative to 'pwd' resource.
####
# Enter the path for your changelog file.
changeLogFile=example-changelog.xml
#### Enter the Target database 'url' information ####
liquibase.command.url=jdbc:h2:tcp://localhost:9090/mem:dev
# Enter the username for your Target database.
liquibase.command.username: dbuser
# Enter the password for your Target database.
liquibase.command.password: letmein
#### Enter the Source Database 'referenceUrl' information ####
## The source database is the baseline or reference against which your target database is compared for diff/diffchangelog commands.
# Enter URL for the source database
liquibase.command.referenceUrl: jdbc:h2:tcp://localhost:9090/mem:integration
# Enter the username for your source database
liquibase.command.referenceUsername: dbuser
# Enter the password for your source database
liquibase.command.referencePassword: letmein
# Logging Configuration
# logLevel controls the amount of logging information generated. If not set, the default logLevel is INFO.
# Valid values, from least amount of logging to most, are:
# OFF, ERROR, WARN, INFO, DEBUG, TRACE, ALL
# If you are having problems, setting the logLevel to DEBUG and re-running the command can be helpful.
# logLevel: DEBUG
# The logFile property controls where logging messages are sent. If this is not set, then logging messages are
# displayed on the console. If this is set, then messages will be sent to a file with the given name.
# logFile: liquibase.log
#### Liquibase Pro Key Information ####
# Learn more, contact support, or get or renew a Pro Key at https://www.liquibase.com/protrial
# liquibase.pro.licensekey:
#### Liquibase Hub Information ####
# Liquibase Hub is a free secure SaaS portal providing status reporting, monitoring & insights
# into your Liquibase database release automation.
# https://hub.liquibase.com
## Add your free Hub API key here
# liquibase.hub.apikey:
# liquibase.hub.mode:all
## Get documentation at docs.liquibase.com ##
## Get certified courses at learn.liquibase.com ##
## Get support at liquibase.com/support ##

54
liquibase-4.9.1/examples/xml/liquibase.sqlcmd.conf Normal file
View File

@ -0,0 +1,54 @@
#### _ _ _ _ _____
## | | (_) (_) | | __ \
## | | _ __ _ _ _ _| |__ __ _ ___ ___ | |__) | __ ___
## | | | |/ _` | | | | | '_ \ / _` / __|/ _ \ | ___/ '__/ _ \
## | |___| | (_| | |_| | | |_) | (_| \__ \ __/ | | | | | (_) |
## \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___| |_| |_| \___/
## | |
## |_|
##
## The liquibase.sqlcmd.conf file stores properties which are used during the
## execution of the Microsoft SQLCMD tool.
## Learn more: https://www.liquibase.org/documentation/config_properties.html
####
####
## Note about relative and absolute paths:
## The liquibase.sqlcmd.path must be a valid path to the SQLCMD executable.
## The liquibase.sqlcmd.timeout value can be one of:
## -1 - disable the timeout
## Any integer value > 0 (measured in seconds)
##
####
# The full path to the SQLCMD executable.
# Sample Linux path
# liquibase.sqlcmd.path=/opt/mssql-tools/bin/sqlcmd
# Sample Windows path
# liquibase.sqlcmd.path="C:\\Program Files\\Microsoft SQL Server\\Client SDK\\ODBC\\170\\Tools\\Binn\\SQLCMD.EXE"
# A valid timeout value for the execution of the SQLCMD tool
liquibase.sqlcmd.timeout=-1
# Flag to indicate whether or not to keep the temporary SQL file after execution of SQLCMD.
# True = keep False = delete (default)
liquibase.sqlcmd.keep.temp=true
# OPTIONAL Flag to designate the location to store temporary SQL file after execution of SQLCMD.
# Liquibase will attempt to use path exactly as entered, so please ensure it complies with your OS requirements.
# liquibase.sqlcmd.keep.temp.path=
# OPTIONAL Flag to designate the name of temporary SQL file after execution of SQLCMD.
# Liquibase will attempt to use the name exactly as entered, so please ensure it complies with your OS requirements.
# liquibase.sqlcmd.keep.temp.name=
# OPTIONAL Args to pass directly to SQLCMD.
# Learn about SQLCMD args at https://<link>
# Note: The delimiter for args is a space eg:" " and not "," or ";" separated.
# liquibase.sqlcmd.args=
# OPTIONAL Path to a log file for the SQLCMD output
# liquibase.sqlcmd.logFile=
# OPTIONAL Name of a custom executor to use instead of SQLCMD
# The Executor must be on the Liquibase classpath
# liquibase.sqlcmd.executor=

51
liquibase-4.9.1/examples/xml/liquibase.sqlplus.conf Normal file
View File

@ -0,0 +1,51 @@
#### _ _ _ _ _____
## | | (_) (_) | | __ \
## | | _ __ _ _ _ _| |__ __ _ ___ ___ | |__) | __ ___
## | | | |/ _` | | | | | '_ \ / _` / __|/ _ \ | ___/ '__/ _ \
## | |___| | (_| | |_| | | |_) | (_| \__ \ __/ | | | | | (_) |
## \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___| |_| |_| \___/
## | |
## |_|
##
## The liquibase.sqlplus.conf file stores properties which are used during the
## execution of the Oracle SQLPLUS tool.
## Learn more: https://www.liquibase.org/documentation/config_properties.html
####
####
## Note about relative and absolute paths:
## The liquibase.sqlplus.path must be a valid path to the SQLPlUS executable.
## The liquibase.sqlplus.timeout value can be one of:
## -1 - disable the timeout
## Any integer value > 0 (measured in seconds)
##
####
# The full path to the SQLPLUS executable.
# Sample Linux path
# liquibase.sqlplus.path=/apps/app/12.2.0.1.0/oracle/product/12.2.0.1.0/client_1/bin/sqlplus
# Sample Windows path
# liquibase.sqlplus.path=c:\\oracle\\product\\11.2.0\\client_1\\bin\\sqlplus.exe
# A valid timeout value for the execution of the SQLPLUS tool
liquibase.sqlplus.timeout=-1
# Flag to indicate whether or not to keep the temporary SQL file after execution of SQLPLUS.
# True = keep False = delete (default)
liquibase.sqlplus.keep.temp=true
# OPTIONAL Flag to designate the location to store temporary SQL file after execution of SQLPLUS.
# Liquibase will attempt to use path exactly as entered, so please ensure it complies with your OS requirements.
# liquibase.sqlplus.keep.temp.path=
# OPTIONAL Flag to designate the name of temporary SQL file after execution of SQLPLUS.
# Liquibase will attempt to use the name exactly as entered, so please ensure it complies with your OS requirements.
# liquibase.sqlplus.keep.temp.name=
# OPTIONAL Args to pass directly to SQLPLUS.
# Learn about SQLPLUS args at https://docs.oracle.com/cd/B10501_01/server.920/a90842/ch4.htm
# Note: The delimiter for args is a space eg:" " and not "," or ";" separated.
# liquibase.sqlplus.args=
# OPTIONAL Name of a custom executor to use instead of SQLPLUS
# The Executor must be on the Liquibase classpath
# liquibase.sqlplus.executor=

12
liquibase-4.9.1/examples/yaml/blank-changelog.yaml Normal file
View File

@ -0,0 +1,12 @@
databaseChangeLog:
- changeSet:
id: 1
author: your.name
changes:
# Insert Yaml change objects here https://www.liquibase.org/documentation/yaml_format.html
- changeSet:
id: 2
author: your.name
changes:
# Insert Yaml change objects here https://www.liquibase.org/documentation/yaml_format.html

78
liquibase-4.9.1/examples/yaml/example-changelog.yaml Normal file
View File

@ -0,0 +1,78 @@
databaseChangeLog:
- changeSet:
id: 1
author: your.name
labels: example-label
context: example-context
comment: example-comment
changes:
- createTable:
tableName: person
columns:
- column:
name: id
type: int
autoIncrement: true
constraints:
primaryKey: true
nullable: false
- column:
name: name
type: varchar(50)
constraints:
nullable: false
- column:
name: address1
type: varchar(50)
- column:
name: address2
type: varchar(50)
- column:
name: city
type: varchar(30)
- changeSet:
id: 2
author: your.name
labels: example-label
context: example-context
comment: example-comment
changes:
- createTable:
tableName: company
columns:
- column:
name: id
type: int
autoIncrement: true
constraints:
primaryKey: true
nullable: false
- column:
name: name
type: varchar(50)
constraints:
nullable: false
- column:
name: address1
type: varchar(50)
- column:
name: address2
type: varchar(50)
- column:
name: city
type: varchar(30)
- changeSet:
id: 3
author: other.dev
labels: example-label
context: example-context
comment: example-comment
changes:
- addColumn:
tableName: person
columns:
- column:
name: country
type: varchar(2)

17
liquibase-4.9.1/examples/yaml/example-changeset-yaml.txt Normal file
View File

@ -0,0 +1,17 @@
- changeSet:
id: 1
author: dev
changes:
- createTable:
tableName: person
columns:
- column:
name: id
type: int
autoIncrement: true
constraints:
primaryKey: true
nullable: false
- column:
name: name
type: varchar(255)

76
liquibase-4.9.1/examples/yaml/liquibase.properties Normal file
View File

@ -0,0 +1,76 @@
#### _ _ _ _
## | | (_) (_) |
## | | _ __ _ _ _ _| |__ __ _ ___ ___
## | | | |/ _` | | | | | '_ \ / _` / __|/ _ \
## | |___| | (_| | |_| | | |_) | (_| \__ \ __/
## \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|
## | |
## |_|
##
## The liquibase.properties file stores properties which do not change often,
## such as database connection information. Properties stored here save time
## and reduce risk of mistyped command line arguments.
## Learn more: https://www.liquibase.org/documentation/config_properties.html
####
####
## Note about relative and absolute paths:
## The liquibase.properties file requires paths for some properties.
## The classpath is the path/to/resources (ex. src/main/resources).
## The changeLogFile path is relative to the classpath.
## The url H2 example below is relative to 'pwd' resource.
####
# Enter the path for your changelog file.
changeLogFile=example-changelog.yaml
#### Enter the Target database 'url' information ####
liquibase.command.url=jdbc:h2:tcp://localhost:9090/mem:dev
# Enter the username for your Target database.
liquibase.command.username: dbuser
# Enter the password for your Target database.
liquibase.command.password: letmein
#### Enter the Source Database 'referenceUrl' information ####
## The source database is the baseline or reference against which your target database is compared for diff/diffchangelog commands.
# Enter URL for the source database
liquibase.command.referenceUrl: jdbc:h2:tcp://localhost:9090/mem:integration
# Enter the username for your source database
liquibase.command.referenceUsername: dbuser
# Enter the password for your source database
liquibase.command.referencePassword: letmein
# Logging Configuration
# logLevel controls the amount of logging information generated. If not set, the default logLevel is INFO.
# Valid values, from least amount of logging to most, are:
# OFF, ERROR, WARN, INFO, DEBUG, TRACE, ALL
# If you are having problems, setting the logLevel to DEBUG and re-running the command can be helpful.
# logLevel: DEBUG
# The logFile property controls where logging messages are sent. If this is not set, then logging messages are
# displayed on the console. If this is set, then messages will be sent to a file with the given name.
# logFile: liquibase.log
#### Liquibase Pro Key Information ####
# Learn more, contact support, or get or renew a Pro Key at https://www.liquibase.com/protrial
# liquibase.pro.licensekey:
#### Liquibase Hub Information ####
# Liquibase Hub is a free secure SaaS portal providing status reporting, monitoring & insights
# into your Liquibase database release automation.
# https://hub.liquibase.com
## Add your free Hub API key here
# liquibase.hub.apikey:
# liquibase.hub.mode:all
## Get documentation at docs.liquibase.com ##
## Get certified courses at learn.liquibase.com ##
## Get support at liquibase.com/support ##

BIN
liquibase-4.9.1/lib/h2-2.1.210.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/hsqldb-2.5.2.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/jaxb-api-2.3.0.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/jaxb-core-2.3.0.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/jaxb-impl-2.3.0.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/jaybird-4.0.3.java8.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/jcc-11.5.6.0.jar Normal file
View File

Binary file not shown.

162
liquibase-4.9.1/lib/liquibase_autocomplete.sh Normal file
View File

@ -0,0 +1,162 @@
_liquibase()
{
local cur prev opts
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
prev="${COMP_WORDS[COMP_CWORD-1]}"
# Liquibase options, has to be improved to be more context aware
opts="
help
update
updateSQL
updateCount
updateCountSQL
updateToTag
updateToTagSQL
status
registerChangeLog
syncHub
rollback
rollbackSQL
rollbackOneChangeSet
rollbackOneChangeSetSQL
rollbackOneUpdate
rollbackOneUpdateSQL
rollbackToDate
rollbackToDateSQL
rollbackCount
rollbackCountSQL
futureRollbackSQL
futureRollbackFromTagSQL
updateTestingRollback
generateChangeLog
snapshot
snapshotReference
diff
diffChangeLog
dbDoc
history
tag
tagExists
status
unexpectedChangeSets
validate
calculateCheckSum
clearCheckSums
changelogSync
changelogSyncSQL
changeLogSyncToTag
changeLogSyncToTagSQL
checks^show
checks^run
checks^bulk-set
checks^delete^--check-name=<check_short_name>
checks^customize^--check-name=<check_short_name>
checks^enable^--check-name=<check_short_name>
checks^disable^--check-name=<check_short_name>
checks^copy^--check-name=<check_short_name>
checks^reset^--check-name=<check_short_name>
markNextChangeSetRan
markNextChangeSetRanSQL
listLocks
releaseLocks
dropAll
--changeLogFile
--changeSetAuthor=<author>
--changeSetId=<id>
--changeSetPath=<changelogFile>
--deploymentId=<deploymentId>
--force
--format
--username
--password
--url
--classpath
--driver
--databaseClass
--propertyProviderClass
--defaultSchemaName
--contexts
--labels
--defaultsFile
--delimiter
--driverPropertiesFile
--changeExecListenerClass
--changeExecListenerPropertiesFile
--liquibaseCatalogName
--liquibaseSchemaName
--databaseChangeLogTableName
--databaseChangeLogLockTableName
--databaseChangeLogTablespaceName
--liquibaseSchemaName
--includeSystemClasspath
--overwriteOutputFile
--promptForNonLocalDatabase
--logLevel
--logFile
--currentDateTimeFunction
--outputDefaultSchema
--outputDefaultCatalog
--outputFile
--rollbackScript
--excludeObjects
--includeObjects
--help
--version
--snapshotFormat
--referenceUsername
--referencePassword
--referenceUrl
--defaultCatalogName
--defaultSchemaName
--referenceDefaultCatalogName
--referenceDefaultSchemaName
--schemas
--referenceSchemas
--outputSchemaAs
--includeCatalog
--includeSchema
--includeTablespace
--referenceDriver
--dataOutputDirectory
--diffTypes
--diffTypes=<catalog,tables,functions,views,columns,indexes,foreignkeys,primarykeys,uniqueconstraints,data,storedprocedure,triggers,sequences> -D<property.name>=<property.value>
--verbose
--liquibaseProLicenseKey"
# Handle --xxxxxx=
if [[ ${prev} == "--"* && ${cur} == "=" ]] ; then
COMPREPLY=(*)
return 0
fi
# Handle --xxxxx=path
if [[ ${prev} == '=' ]] ; then
# Unescape space
cur=${cur//\\ / }
# Expand tilder to $HOME
[[ ${cur} == "~/"* ]] && cur=${cur/\~/$HOME}
# Show completion if path exist (and escape spaces)
local files=("${cur}"*)
[[ -e ${files[0]} ]] && COMPREPLY=( "${files[@]// /\ }" )
return 0
fi
# Handle other options
COMPREPLY=( $(compgen -W "${opts}" -- "${cur}") )
if [[ ${#COMPREPLY[@]} == 1 && ${COMPREPLY[0]} != "--"*"=" ]] ; then
# If there's only one option, without =, then allow a space
compopt +o nospace
fi
# Handle subcommands
for i in "${!COMPREPLY[@]}"; do
temp="${COMPREPLY[$i]}"
COMPREPLY[$i]="${temp//\^/ }"
done
return 0
}
complete -o nospace -F _liquibase liquibase

112
liquibase-4.9.1/lib/liquibase_autocomplete_mac.bash Executable file
View File

@ -0,0 +1,112 @@
#/usr/bin/env bash
complete -W \
"help \
update \
updateSQL \
updateCount \
updateCountSQL \
updateToTag \
updateToTagSQL \
'status --verbose' \
'registerChangeLog --changeLogFile=<changelogFile>' \
'syncHub --changeLogFile=<changelogFile>' \
rollback \
rollbackSQL \
'rollbackOneChangeSet --changeSetAuthor=<author> --changeSetId=<id> --changeSetPath=<changelogFile> --force' \
'rollbackOneChangeSetSQL --changeSetAuthor=<author> --changeSetId=<id> --changeSetPath=<changelogFile>' \
'rollbackOneUpdate --deploymentId=<deploymentId> --force' \
'rollbackOneUpdateSQL --deploymentId=<deploymentId>' \
rollbackToDate \
rollbackToDateSQL \
rollbackCount \
rollbackCountSQL \
futureRollbackSQL \
futureRollbackFromTagSQL \
updateTestingRollback \
generateChangeLog \
snapshot \
snapshotReference \
diff \
diffChangeLog \
dbDoc \
history \
tag \
tagExists \
status \
unexpectedChangeSets \
validate \
calculateCheckSum \
clearCheckSums \
changelogSync \
changelogSyncSQL \
markNextChangeSetRan \
markNextChangeSetRanSQL \
listLocks \
releaseLocks \
dropAll \
'checks run' \
'checks delete --check-name=<check_short_name>' \
'checks bulk-set' \
'checks show' \
'checks customize --check-name=<check_short_name>' \
'checks reset --check-name=<check_short_name>' \
'checks enable --check-name=<check_short_name>' \
'checks disable --check-name=<check_short_name>' \
'checks copy --check-name=<check_short_name>' \
--changeLogFile \
--username \
--password \
--url \
--classpath \
--driver \
--databaseClass \
--propertyProviderClass \
--defaultSchemaName \
--contexts \
--labels \
--defaultsFile \
--delimiter \
--driverPropertiesFile \
--changeExecListenerClass \
--changeExecListenerPropertiesFile \
--liquibaseCatalogName \
--liquibaseSchemaName \
--databaseChangeLogTableName \
--databaseChangeLogLockTableName \
--databaseChangeLogTablespaceName \
--liquibaseSchemaName \
--includeSystemClasspath \
--overwriteOutputFile \
--promptForNonLocalDatabase \
--logLevel \
--logFile \
--currentDateTimeFunction \
--outputDefaultSchema \
--outputDefaultCatalog \
--outputFile \
--rollbackScript \
--excludeObjects \
--includeObjects \
--help \
--version \
--snapshotFormat \
--referenceUsername \
--referencePassword \
--referenceUrl \
--defaultCatalogName \
--defaultSchemaName \
--referenceDefaultCatalogName \
--referenceDefaultSchemaName \
--schemas \
--referenceSchemas \
--outputSchemaAs \
--includeCatalog \
--includeSchema \
--includeTablespace \
--referenceDriver \
--dataOutputDirectory \
--diffTypes \
--diffTypes=<catalog,tables,functions,views,columns,indexes,foreignkeys,primarykeys,uniqueconstraints,data,storedprocedure,triggers,sequences> -D<property.name>=<property.value> \
--format \
--liquibaseProLicenseKey" liquibase

BIN
liquibase-4.9.1/lib/mariadb-java-client-2.7.0.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/mssql-jdbc-8.4.0.jre8.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/ojdbc8-18.3.0.0.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/picocli-4.6.1.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/postgresql-42.3.2.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/snakeyaml-1.27.jar Normal file
View File

Binary file not shown.

BIN
liquibase-4.9.1/lib/sqlite-jdbc-3.34.0.jar Normal file
View File

Binary file not shown.

182
liquibase-4.9.1/licenses/Liquibase Pro EULA Software License Subscription and Support Agreement.txt Normal file
View File

@ -0,0 +1,182 @@
SOFTWARE LICENSE SUBSCRIPTION AND SUPPORT AGREEMENT
PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THIS SERVICE.
BY USING THE SOFTWARE OR CLICKING AGREE, CUSTOMER IS AGREEING TO BE BOUND BY
THIS AGREEMENT. IF YOU ARE AGREEING TO THIS AGREEMENT ON BEHALF OF OR FOR THE
BENEFIT OF YOUR EMPLOYER OR A THIRD PARTY, THEN YOU REPRESENT AND WARRANT THAT
YOU HAVE THE NECESSARY AUTHORITY TO AGREE TO THIS AGREEMENT ON YOUR EMPLOYER'S
OR THAT THIRD PARTY'S BEHALF.
This agreement is between Liquibase, Inc. a Delaware corporation (Liquibase) and
you, the customer entering into this agreement (Customer). The LiquibasePro
software, updates, documentation and license keys provided to Customer
(Software) are licensed and are not sold.
SCOPE. This agreement describes the licensing of the Software and support
provided to Customer under an order. Third party contractors and majority owned
affiliates of Customer can use and access the Software under the terms of this
agreement, and Customer is responsible for each of their compliance with such
terms.
1. LICENSE. Subject to the other terms of this agreement, Liquibase grants
Customer, under an order, a term based non-exclusive, non-transferable license
up to the license capacity purchased to use the Software only in Customer’s
internal business operations. Third party licenses delivered with the Software
may be subject to additional license rights and restrictions a set forth at
https://download.liquibase.org/lbpro-third-party-licenses/.
2. RESTRICTIONS. Customer may not:
a. Transfer, assign, sublicense, rent the Software, create derivative works of
the Software, or use it in any type of service provider environment;
b. Reverse engineer, decompile, disassemble, or translate the Software; or
c. Evaluate the Software for the purpose of competing with Liquibase Pro or
operate the Software other than in accordance with its technical documentation.
3. PROPRIETARY RIGHTS AND MUTUAL CONFIDENTIALITY.
a. Proprietary Rights. The Software, workflow processes, user interface,
designs and other technologies provided by Liquibase as part of the Software are
the proprietary property of Liquibase and its licensors, and all right, title and
interest in and to such items, including all associated intellectual property
rights, remain only with Liquibase and its licensors. The Software is protected
by copyright and other intellectual property laws. Customer may not remove any
product identification, copyright, trademark or other notice from the Software.
Liquibase reserves all rights not expressly granted.
b. Mutual Confidentiality. Recipient may not disclose Confidential Information
of Discloser to any third party or use the Confidential Information in
violation of this agreement.
Confidential Information means all information that is disclosed to the
recipient (Recipient) by the discloser (Discloser), and includes, among other
things:
* any and all information relating to products or services provided by a
Discloser, software code, flow charts, techniques, specifications, development
and marketing plans, strategies, and forecasts;
* as to Liquibase, the Software and the terms of this agreement, including
without limitation, all pricing information.
Confidential Information excludes information that:
* was rightfully in Recipient's possession without any obligation of
confidentiality before receipt from the Discloser;
* is or becomes a matter of public knowledge through no fault of Recipient;
* is rightfully received by Recipient from a third party without violation of
a duty of confidentiality; or
* is independently developed by or for Recipient without use or access to the
Confidential Information.
Recipient may disclose Confidential Information if required by law, but it will
attempt to provide notice to the Discloser in advance so it may seek a
protective order. Each party acknowledges that any misuse of the other party’s
Confidential Information may cause irreparable harm for which there is no
adequate remedy at law. Either party may seek immediate injunctive relief in
such event.
4. WARRANTY, REMEDY and DISCLAIMER. For new license purchases, Liquibase warrants
that the Software will perform in substantial accordance with its accompanying
technical documentation for a period of 60 days from the date of the order.
This warranty will not apply to any problems caused by software not licensed to
Customer by Liquibase, use other than in accordance with the technical
documentation, or misuse of the Software. The warranty only covers problems
reported to Liquibase during the warranty period or 30 days after. Customer will
cooperate with Liquibase in resolving any warranty claim.
A. EXCLUSIVE REMEDY AND SOLE LIABILITY. Liquibase will use commercially
reasonable efforts to remedy covered warranty claims within a reasonable period
of time or replace the Software, or if Liquibase cannot do so it will refund to
Customer the license fee paid. THIS REMEDY IS CUSTOMER’S EXCLUSIVE REMEDY, AND
LIQUIBASE’S SOLE LIABILITY FOR THESE WARRANTY CLAIMS.
B. DISCLAIMER OF WARRANTIES. LIQUIBASE DISCLAIMS ALL OTHER EXPRESS AND IMPLIED
WARRANTIES, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTY OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMER UNDERSTANDS THAT
THE SOFTWARE MAY NOT BE ERROR FREE, AND USE MAY BE INTERRUPTED.
5. TERMINATION. This agreement expires at the end of the license period
specified. Either party may terminate this agreement upon a material breach of
the other party after a 30 days’ notice/cure period, if the breach is not cured
during such time period. Upon terminationof this agreement or a license,
Customer must discontinue using the Software, de-install and destroy or return
the Software and all copies, within 5 days. Upon Liquibase's request, Customer
will provide written certification of such compliance.
6. SUPPORT. Liquibase’s technical support and maintenance services (Support) is
included with the license fees. Customer will receive best efforts e-mail
response for support within two business days from receipt of issue. Liquibase
may change its Support terms, but Support will not materially degrade during
any Support term.
7. LIMIT ON LIABILITY. There may be situations in which (as a result of
material breach or other liability) Customer is entitled to make a claim
against Liquibase. In each situation (regardless of the form of the legal action
(e.g. contract or tort claims)), Liquibase is not responsible for any damage and
does not have any liability beyond the greater of the amount paid or payable by
Customer to Liquibase within the 12 months prior to the event that gave rise to
the claim and in no event is Liquibase responsible for any: loss of data or
information; lost profits, revenue, or productivity; or other special,
consequential, incidental or indirect damages.
8. INTELLECTUAL PROPERTY INDEMNITY
a. Defense of Third Party Claims. Liquibase will defend or settle any third party
claim against Customer to the extent that such claim alleges that the Software
violates a copyright, patent, trademark or other intellectual property right,
if Customer, promptly notifies Liquibase of the claim in writing, cooperates with
Liquibase in the defense, and allows Liquibase to solely control the defense or
settlement of the claim. Costs. Liquibase will pay infringement claim defense
costs incurred as part of its obligations above, and Liquibase negotiated
settlement amounts, and court awarded damages. Process. If such a claim appears
likely, then Liquibase may modify the Software, procure the necessary rights, or
replace it with the functional equivalent. If Liquibase determines that none of
these are reasonably available, then Liquibase may terminate the Software and
refund any prepaid and unused fees. Exclusions. Liquibase has no obligation for
any claim arising from: Liquibase’s compliance with Customer’s specifications; A
combination of the Software with other technology where the infringement would
not occur but for the combination; or Technology not provided by Liquibase. THIS
SECTION CONTAINS CUSTOMER’S EXCLUSIVE REMEDIES AND LIQUIBASE’S SOLE LIABILITY FOR
INTELLECTUAL PROPERTY INFRINGEMENT CLAIMS.
9. GOVERNING LAW AND EXCLUSIVE FORUM. This agreement is governed by the laws of
the State of Delaware (without regard to conflicts of law principles) for any
dispute between the parties or relating in any way to the subject matter of
this agreement. Any suit or legal proceeding must be exclusively brought in the
federal or state courts for Travis County, Texas, and Customer submits to this
personal jurisdiction and venue. Nothing in this agreement prevents either
party from seeking injunctive relief in a court of competent jurisdiction. The
prevailing party in litigation is entitled to recover its attorneys’ fees and
costs from the other party.
10. OTHER TERMS.
a. Entire Agreement. This agreement and the order constitute the entire
agreement between the parties and supersede any prior or contemporaneous
negotiations or agreements, whether oral or written, related to this subject
matter. Customer is not relying on any representation concerning this subject
matter, oral or written, not included in this agreement. No representation,
promise or inducement not included in this agreement is binding.
b. Non-Assignment. Neither party may assign or transfer this agreement to a
third party, nor delegate any duty, except that the agreement and all orders
may be assigned, without the consent of the other party, as part of a merger,
or sale of all or substantially all of the business or assets, of a party.
c. Independent Contractors. The parties are independent contractors with
respect to each other.
d. Enforceability. If any term of this agreement is invalid or unenforceable,
the other terms remain in effect.
e. Survival of Terms and Force Majeure. All terms that by their nature survive
termination of this agreement for each party to receive the benefits and
protections of this agreement, will survive. Neither party is liable for events
beyond its reasonable control, including, without limitation force majeure
events.
f. Modification Only in Writing. No modification or waiver of any term of this
agreement is effective unless signed by both parties.
g. Export Compliance. Customer must comply with all applicable export control
laws of the United States, foreign jurisdictions and other applicable laws and
regulations.
h. US GOVERNMENT RESTRICTED RIGHTS. If Customer is a United States government
agency or acquired the license to the Software hereunder pursuant to a
government contract or with government funds, then as defined in FAR §2.101,
DFAR §252.227-7014(a)(1) and DFAR §252.227-7014(a)(5) or otherwise, all
Software provided in connection with this agreement are “commercial items,”
“commercial computer software” or “commercial computer software documentation.”
Consistent with DFAR §227.7202 and FAR §12.212, any use, modification,
reproduction, release, performance, display, disclosure or distribution by or
for the United States government is governed solely by the terms of this
agreement and is prohibited except to the extent permitted by the terms of this
agreement.
i. No PO Terms. Liquibase rejects conflicting terms of a Customer’s
form-purchasing document.
j. Order of Precedence. If there is an inconsistency between this agreement and
an order, the order prevails.

87
liquibase-4.9.1/licenses/README.txt Normal file
View File

@ -0,0 +1,87 @@
Liquibase License Information
Version: 4.9.1
Liquibase ships with 3rd party components using the following licenses:
- Apache 2.0 License - https://opensource.org/licenses/Apache-2.0
- BSD 2 Clause License - https://opensource.org/licenses/BSD-2-Clause
- CDDL 1.1 License - https://opensource.org/licenses/cddl1.txt
- CPL 1.0 License - https://opensource.org/licenses/CPL-1.0
- Eclipse Public 1.0 License - https://opensource.org/licenses/epl-1.0
- ISC License - https://opensource.org/licenses/ISC
- LPGL 3.0 License - https://opensource.org/licenses/LGPL-3.0
- MIT License - https://opensource.org/licenses/MIT
- Plexus Classworlds License - https://spdx.org/licenses/Plexus.html
Libraries and their licenses:
Apache 2.0 License
- avalon-framework:avalon-framework
- commons-logging:commons-logging
- doxia:doxia-sink-api
- javax.enterprise:cdi-api
- javax.inject:javax.inject
- org.apache.ant:ant
- org.apache.ant:ant-launcher
- org.apache.maven:maven-artifact
- org.apache.maven:maven-artifact-manager
- org.apache.maven:maven-core
- org.apache.maven:maven-error-diagnostics
- org.apache.maven:maven-model
- org.apache.maven:maven-monitor
- org.apache.maven:maven-plugin-api
- org.apache.maven:maven-plugin-descriptor
- org.apache.maven:maven-plugin-parameter-documenter
- org.apache.maven:maven-plugin-registry
- org.apache.maven:maven-profile
- org.apache.maven:maven-project
- org.apache.maven:maven-repository-metadata
- org.apache.maven:maven-settings
- org.apache.maven.reporting:maven-reporting-api
- org.apache.maven.shared:maven-plugin-testing-harness
- org.apache.maven.shared:maven-verifier
- org.apache.maven.wagon:wagon-file
- org.apache.maven.wagon:wagon-http-lightweight
- org.apache.maven.wagon:wagon-provider-api
- org.apache.maven.wagon:wagon-ssh
- org.codehaus.plexus:plexus-archiver
- org.codehaus.plexus:plexus-container-default
- org.codehaus.plexus:plexus-interactivity-api
- org.codehaus.plexus:plexus-utils
- org.jboss.weld.se:weld-se
- org.liquibase:liquibase-cdi
- org.liquibase:liquibase-core
- org.liquibase:liquibase-debian
- org.liquibase:liquibase-maven-plugin
- org.liquibase:liquibase-parent
- org.springframework:spring
- org.yaml:snakeyaml
- snakeyaml.jar
BSD 2 Clause License
- com.jcraft:jsch
- org.hamcrest:hamcrest-core
- org.hsqldb:hsqldb
- org.postgresql:postgresql
CDDL 1.1 License
- javax.annotation:jsr250-api
- javax.servlet:servlet-api (Dual license: CDDL-1.1, GPL-2.0)
- jaxb-api.jar
- jaxb-core.jar
- jaxb-impl.jar
CPL 1.0 License
- junit:junit
Eclipse Public License 1.0
- h2.jar
ISC License
- logkit:logkit
LGPL-3.0 license
- org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec
Plexus Classworlds License
- classworlds:classworlds

65
liquibase-4.9.1/licenses/apache-2.0.txt Normal file
View File

@ -0,0 +1,65 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License.
Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution.
You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions.
Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks.
This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty.
Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability.
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability.
While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

9
liquibase-4.9.1/licenses/bsd-2-clause.txt Normal file
View File

@ -0,0 +1,9 @@
The 2-Clause BSD License
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

131
liquibase-4.9.1/licenses/cddl1.txt Normal file
View File

@ -0,0 +1,131 @@
COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0
1. Definitions.
1.1. "Contributor" means each individual or entity that creates or contributes to the creation of Modifications.
1.2. "Contributor Version" means the combination of the Original Software, prior Modifications used by a Contributor (if any), and the Modifications made by that particular Contributor.
1.3. "Covered Software" means (a) the Original Software, or (b) Modifications, or (c) the combination of files containing Original Software with files containing Modifications, in each case including portions thereof.
1.4. "Executable" means the Covered Software in any form other than Source Code.
1.5. "Initial Developer" means the individual or entity that first makes Original Software available under this License.
1.6. "Larger Work" means a work which combines Covered Software or portions thereof with code not governed by the terms of this License.
1.7. "License" means this document.
1.8. "Licensable" means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein.
1.9. "Modifications" means the Source Code and Executable form of any of the following:
A. Any file that results from an addition to, deletion from or modification of the contents of a file containing Original Software or previous Modifications;
B. Any new file that contains any part of the Original Software or previous Modification; or
C. Any new file that is contributed or otherwise made available under the terms of this License.
1.10. "Original Software" means the Source Code and Executable form of computer software code that is originally released under this License.
1.11. "Patent Claims" means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor.
1.12. "Source Code" means (a) the common form of computer software code in which modifications are made and (b) associated documentation included in or with such code.
1.13. "You" (or "Your") means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.
2. License Grants.
2.1. The Initial Developer Grant.
Conditioned upon Your compliance with Section 3.1 below and subject to third party intellectual property claims, the Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license:
(a) under intellectual property rights (other than patent or trademark) Licensable by Initial Developer, to use, reproduce, modify, display, perform, sublicense and distribute the Original Software (or portions thereof), with or without Modifications, and/or as part of a Larger Work; and
(b) under Patent Claims infringed by the making, using or selling of Original Software, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Software (or portions thereof).
(c) The licenses granted in Sections 2.1(a) and (b) are effective on the date Initial Developer first distributes or otherwise makes the Original Software available to a third party under the terms of this License.
(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code that You delete from the Original Software, or (2) for infringements caused by: (i) the modification of the Original Software, or (ii) the combination of the Original Software with other software or devices.
2.2. Contributor Grant.
Conditioned upon Your compliance with Section 3.1 below and
subject to third party intellectual property claims, each
Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license:
(a) under intellectual property rights (other than patent or trademark) Licensable by Contributor to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof), either on an unmodified basis, with other Modifications, as Covered Software and/or as part of a Larger Work; and
(b) under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or portions thereof); and (2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination).
(c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first distributes or otherwise makes the Modifications available to a third party.
(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any code that Contributor has deleted from the Contributor Version; (2) for infringements caused by: (i) third party modifications of Contributor Version, or (ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or (3) under Patent Claims infringed by Covered Software in the absence of Modifications made by that Contributor.
3. Distribution Obligations.
3.1. Availability of Source Code.
Any Covered Software that You distribute or otherwise make available in Executable form must also be made available in Source Code form and that Source Code form must be distributed only under the terms of this License. You must include a copy of this License with every copy of the Source Code form of the Covered Software You distribute or otherwise make available. You must inform recipients of any such Covered Software in Executable form as to how they can obtain such Covered Software in Source Code form in a reasonable manner on or through a medium customarily used for software exchange.
3.2. Modifications.
The Modifications that You create or to which You contribute are governed by the terms of this License. You represent that You believe Your Modifications are Your original creation(s) and/or You have sufficient rights to grant the rights conveyed by this License.
3.3. Required Notices.
You must include a notice in each of Your Modifications that identifies You as the Contributor of the Modification. You may not remove or alter any copyright, patent or trademark notices contained within the Covered Software, or any notices of licensing or any descriptive text giving attribution to any Contributor or the Initial Developer.
3.4. Application of Additional Terms.
You may not offer or impose any terms on any Covered Software in Source Code form that alters or restricts the applicable version of this License or the recipients' rights hereunder. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Software. However, you may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear that any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer.
3.5. Distribution of Executable Versions.
You may distribute the Executable form of the Covered Software under the terms of this License or under the terms of a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable form does not attempt to limit or alter the recipient's rights in the Source Code form from the rights set forth in this License. If You distribute the Covered Software in Executable form under a different license, You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer.
3.6. Larger Works.
You may create a Larger Work by combining Covered Software with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Software.
4. Versions of the License.
4.1. New Versions.
Sun Microsystems, Inc. is the initial license steward and may publish revised and/or new versions of this License from time to time. Each version will be given a distinguishing version number. Except as provided in Section 4.3, no one other than the license steward has the right to modify this License.
4.2. Effect of New Versions.
You may always continue to use, distribute or otherwise make the Covered Software available under the terms of the version of the License under which You originally received the Covered Software. If the Initial Developer includes a notice in the Original Software prohibiting it from being distributed or otherwise made available under any subsequent version of the License, You must distribute and make the Covered Software available under the terms of the version of the License under which You originally received the Covered Software. Otherwise, You may also choose to use, distribute or otherwise make the Covered Software available under the terms of any subsequent version of the License published by the license steward.
4.3. Modified Versions.
When You are an Initial Developer and You want to create a new license for Your Original Software, You may create and use a modified version of this License if You: (a) rename the license and remove any references to the name of the license steward (except to note that the license differs from this License); and (b) otherwise make it clear that the license contains terms which differ from this License.
5. DISCLAIMER OF WARRANTY.
COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
6. TERMINATION.
6.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive.
6.2. If You assert a patent infringement claim (excluding declaratory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You assert such claim is referred to as "Participant") alleging that the Participant Software (meaning the Contributor Version where the Participant is a Contributor or the Original Software where the Participant is the Initial Developer) directly or indirectly infringes any patent, then any and all rights granted directly or indirectly to You by such Participant, the Initial Developer (if the Initial Developer is not the Participant) and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively and automatically at the expiration of such 60 day notice period, unless if within such 60 day period You withdraw Your claim with respect to the Participant Software against such Participant either unilaterally or pursuant to a written agreement with Participant.
6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user licenses that have been validly granted by You or any distributor hereunder prior to termination (excluding licenses granted to You by any distributor) shall survive termination.
7. LIMITATION OF LIABILITY.
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
8. U.S. GOVERNMENT END USERS.
The Covered Software is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" (as that term is defined at 48 C.F.R. ¤ 252.227-7014(a)(1)) and "commercial computer software documentation" as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Software with only those rights set forth herein. This U.S. Government Rights clause is in lieu of, and supersedes, any other FAR, DFAR, or other clause or provision that addresses Government rights in computer software under this License.
9. MISCELLANEOUS.
This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by the law of the jurisdiction specified in a notice contained within the Original Software (except to the extent applicable law, if any, provides otherwise), excluding such jurisdiction's conflict-of-law provisions. Any litigation relating to this License shall be subject to the jurisdiction of the courts located in the jurisdiction and venue specified in a notice contained within the Original Software, with the losing party responsible for costs, including, without limitation, court costs and reasonable attorneys' fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. You agree that You alone are responsible for compliance with the United States export administration regulations (and the export control laws and regulation of any other countries) when You use, distribute or otherwise make available any Covered Software.
10. RESPONSIBILITY FOR CLAIMS.
As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability.

211
liquibase-4.9.1/licenses/cpl-1.0.txt Normal file
View File

@ -0,0 +1,211 @@
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
1. DEFINITIONS
"Contribution" means:
a) in the case of the initial Contributor, the initial code and
documentation distributed under this Agreement, and
b) in the case of each subsequent Contributor:
i) changes to the Program, and
ii) additions to the Program;
where such changes and/or additions to the Program originate from and are
distributed by that particular Contributor. A Contribution 'originates' from a
Contributor if it was added to the Program by such Contributor itself or anyone
acting on such Contributor's behalf. Contributions do not include additions to
the Program which: (i) are separate modules of software distributed in
conjunction with the Program under their own license agreement, and (ii) are not
derivative works of the Program.
"Contributor" means any person or entity that distributes the Program.
"Licensed Patents " mean patent claims licensable by a Contributor which are
necessarily infringed by the use or sale of its Contribution alone or when
combined with the Program.
"Program" means the Contributions distributed in accordance with this Agreement.
"Recipient" means anyone who receives the Program under this Agreement,
including all Contributors.
2. GRANT OF RIGHTS
a) Subject to the terms of this Agreement, each Contributor hereby grants
Recipient a non-exclusive, worldwide, royalty-free copyright license to
reproduce, prepare derivative works of, publicly display, publicly perform,
distribute and sublicense the Contribution of such Contributor, if any, and such
derivative works, in source code and object code form.
b) Subject to the terms of this Agreement, each Contributor hereby grants
Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed
Patents to make, use, sell, offer to sell, import and otherwise transfer the
Contribution of such Contributor, if any, in source code and object code form.
This patent license shall apply to the combination of the Contribution and the
Program if, at the time the Contribution is added by the Contributor, such
addition of the Contribution causes such combination to be covered by the
Licensed Patents. The patent license shall not apply to any other combinations
which include the Contribution. No hardware per se is licensed hereunder.
c) Recipient understands that although each Contributor grants the licenses
to its Contributions set forth herein, no assurances are provided by any
Contributor that the Program does not infringe the patent or other intellectual
property rights of any other entity. Each Contributor disclaims any liability to
Recipient for claims brought by any other entity based on infringement of
intellectual property rights or otherwise. As a condition to exercising the
rights and licenses granted hereunder, each Recipient hereby assumes sole
responsibility to secure any other intellectual property rights needed, if any.
For example, if a third party patent license is required to allow Recipient to
distribute the Program, it is Recipient's responsibility to acquire that license
before distributing the Program.
d) Each Contributor represents that to its knowledge it has sufficient
copyright rights in its Contribution, if any, to grant the copyright license set
forth in this Agreement.
3. REQUIREMENTS
A Contributor may choose to distribute the Program in object code form under its
own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
b) its license agreement:
i) effectively disclaims on behalf of all Contributors all warranties and
conditions, express and implied, including warranties or conditions of title and
non-infringement, and implied warranties or conditions of merchantability and
fitness for a particular purpose;
ii) effectively excludes on behalf of all Contributors all liability for
damages, including direct, indirect, special, incidental and consequential
damages, such as lost profits;
iii) states that any provisions which differ from this Agreement are offered
by that Contributor alone and not by any other party; and
iv) states that source code for the Program is available from such
Contributor, and informs licensees how to obtain it in a reasonable manner on or
through a medium customarily used for software exchange.
When the Program is made available in source code form:
a) it must be made available under this Agreement; and
b) a copy of this Agreement must be included with each copy of the Program.
Contributors may not remove or alter any copyright notices contained within the
Program.
Each Contributor must identify itself as the originator of its Contribution, if
any, in a manner that reasonably allows subsequent Recipients to identify the
originator of the Contribution.
4. COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain responsibilities with
respect to end users, business partners and the like. While this license is
intended to facilitate the commercial use of the Program, the Contributor who
includes the Program in a commercial product offering should do so in a manner
which does not create potential liability for other Contributors. Therefore, if
a Contributor includes the Program in a commercial product offering, such
Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
every other Contributor ("Indemnified Contributor") against any losses, damages
and costs (collectively "Losses") arising from claims, lawsuits and other legal
actions brought by a third party against the Indemnified Contributor to the
extent caused by the acts or omissions of such Commercial Contributor in
connection with its distribution of the Program in a commercial product
offering. The obligations in this section do not apply to any claims or Losses
relating to any actual or alleged intellectual property infringement. In order
to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
Contributor in writing of such claim, and b) allow the Commercial Contributor to
control, and cooperate with the Commercial Contributor in, the defense and any
related settlement negotiations. The Indemnified Contributor may participate in
any such claim at its own expense.
For example, a Contributor might include the Program in a commercial product
offering, Product X. That Contributor is then a Commercial Contributor. If that
Commercial Contributor then makes performance claims, or offers warranties
related to Product X, those performance claims and warranties are such
Commercial Contributor's responsibility alone. Under this section, the
Commercial Contributor would have to defend claims against the other
Contributors related to those performance claims and warranties, and if a court
requires any other Contributor to pay any damages as a result, the Commercial
Contributor must pay those damages.
5. NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
Recipient is solely responsible for determining the appropriateness of using and
distributing the Program and assumes all risks associated with its exercise of
rights under this Agreement, including but not limited to the risks and costs of
program errors, compliance with applicable laws, damage to or loss of data,
programs or equipment, and unavailability or interruption of operations.
6. DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
7. GENERAL
If any provision of this Agreement is invalid or unenforceable under applicable
law, it shall not affect the validity or enforceability of the remainder of the
terms of this Agreement, and without further action by the parties hereto, such
provision shall be reformed to the minimum extent necessary to make such
provision valid and enforceable.
If Recipient institutes patent litigation against a Contributor with respect to
a patent applicable to software (including a cross-claim or counterclaim in a
lawsuit), then any patent licenses granted by that Contributor to such Recipient
under this Agreement shall terminate as of the date such litigation is filed. In
addition, if Recipient institutes patent litigation against any entity
(including a cross-claim or counterclaim in a lawsuit) alleging that the Program
itself (excluding combinations of the Program with other software or hardware)
infringes such Recipient's patent(s), then such Recipient's rights granted under
Section 2(b) shall terminate as of the date such litigation is filed.
All Recipient's rights under this Agreement shall terminate if it fails to
comply with any of the material terms or conditions of this Agreement and does
not cure such failure in a reasonable period of time after becoming aware of
such noncompliance. If all Recipient's rights under this Agreement terminate,
Recipient agrees to cease use and distribution of the Program as soon as
reasonably practicable. However, Recipient's obligations under this Agreement
and any licenses granted by Recipient relating to the Program shall continue and
survive.
Everyone is permitted to copy and distribute copies of this Agreement, but in
order to avoid inconsistency the Agreement is copyrighted and may only be
modified in the following manner. The Agreement Steward reserves the right to
publish new versions (including revisions) of this Agreement from time to time.
No one other than the Agreement Steward has the right to modify this Agreement.
IBM is the initial Agreement Steward. IBM may assign the responsibility to serve
as the Agreement Steward to a suitable separate entity. Each new version of the
Agreement will be given a distinguishing version number. The Program (including
Contributions) may always be distributed subject to the version of the Agreement
under which it was received. In addition, after a new version of the Agreement
is published, Contributor may elect to distribute the Program (including its
Contributions) under the new version. Except as expressly stated in Sections
2(a) and 2(b) above, Recipient receives no rights or licenses to the
intellectual property of any Contributor under this Agreement, whether
expressly, by implication, estoppel or otherwise. All rights in the Program not
expressly granted under this Agreement are reserved.
This Agreement is governed by the laws of the State of New York and the
intellectual property laws of the United States of America. No party to this
Agreement will bring a legal action under this Agreement more than one year
after the cause of action arose. Each party waives its rights to a jury trial in
any resulting litigation.

63
liquibase-4.9.1/licenses/epl-1.0.txt Normal file
View File

@ -0,0 +1,63 @@
GNU LESSER GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
0. Additional Definitions.
As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
1. Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
2. Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
b) Accompany the object code with a copy of the GNU GPL and this license document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
d) Do one of the following:
0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
5. Combined Libraries.
You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
6. Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.

3
liquibase-4.9.1/licenses/isc.txt Normal file
View File

@ -0,0 +1,3 @@
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

125
liquibase-4.9.1/licenses/lgpl-3.0.txt Normal file
View File

@ -0,0 +1,125 @@
GNU LESSER GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
0. Additional Definitions.
As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
1. Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
2. Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
b) Accompany the object code with a copy of the GNU GPL and this license document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
d) Do one of the following:
0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
5. Combined Libraries.
You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
6. Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.GNU LESSER GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.
0. Additional Definitions.
As used herein, “this License” refers to version 3 of the GNU Lesser General Public License, and the “GNU GPL” refers to version 3 of the GNU General Public License.
“The Library” refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
An “Application” is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
A “Combined Work” is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the “Linked Version”.
The “Minimal Corresponding Source” for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
The “Corresponding Application Code” for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
1. Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
2. Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or
b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
b) Accompany the object code with a copy of the GNU GPL and this license document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document.
d) Do one of the following:
0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version.
e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
5. Combined Libraries.
You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following:
a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License.
b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
6. Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.

6
liquibase-4.9.1/licenses/mit.txt Normal file
View File

@ -0,0 +1,6 @@
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

40
liquibase-4.9.1/licenses/plexus.txt Normal file
View File

@ -0,0 +1,40 @@
Copyright 2002 (C) The Codehaus. All Rights Reserved.
Redistribution and use of this software and associated documentation
("Software"), with or without modification, are permitted provided
that the following conditions are met:
1. Redistributions of source code must retain copyright
statements and notices. Redistributions must also contain a
copy of this document.
2. Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other
materials provided with the distribution.
3. The name "classworlds" must not be used to endorse or promote
products derived from this Software without prior written
permission of The Codehaus. For written permission, please
contact bob@codehaus.org.
4. Products derived from this Software may not be called "classworlds"
nor may "classworlds" appear in their names without prior written
permission of The Codehaus. "classworlds" is a registered
trademark of The Codehaus.
5. Due credit should be given to The Codehaus.
(http://classworlds.codehaus.org/).
THIS SOFTWARE IS PROVIDED BY THE CODEHAUS AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE CODEHAUS OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.

91
liquibase-4.9.1/liquibase Executable file
View File

@ -0,0 +1,91 @@
#!/usr/bin/env bash
if [ ! -n "${LIQUIBASE_HOME+x}" ]; then
# echo "LIQUIBASE_HOME is not set."
## resolve links - $0 may be a symlink
PRG="$0"
while [ -h "$PRG" ] ; do
ls=`ls -ld "$PRG"`
link=`expr "$ls" : '.*-> \(.*\)$'`
if expr "$link" : '/.*' > /dev/null; then
PRG="$link"
else
PRG=`dirname "$PRG"`"/$link"
fi
done
LIQUIBASE_HOME=`dirname "$PRG"`
# make it fully qualified
LIQUIBASE_HOME=`cd "$LIQUIBASE_HOME" && pwd`
# echo "Liquibase Home: $LIQUIBASE_HOME"
fi
# build classpath from all jars in lib
if [ -f /usr/bin/cygpath ]; then
CP=.
for i in "$LIQUIBASE_HOME"/liquibase*.jar; do
i=`cygpath --windows "$i"`
CP="$CP;$i"
done
# Gather jars from a local liquibase_libs directory
for i in liquibase_libs/*.jar; do
i=`cygpath --windows "$i"`
CP="$CP;$i"
done
for i in "$LIQUIBASE_HOME"/lib/*.jar; do
i=`cygpath --windows "$i"`
CP="$CP;$i"
done
else
if [[ $(uname) = MINGW* ]]; then
CP_SEPARATOR=";"
else
CP_SEPARATOR=":"
fi
CP=.
for i in "$LIQUIBASE_HOME"/liquibase*.jar; do
CP="$CP""$CP_SEPARATOR""$i"
done
# Gather jars from a local liquibase_libs directory
CP="$CP""$CP_SEPARATOR""liquibase_libs/"
for i in liquibase_libs/*.jar; do
CP="$CP""$CP_SEPARATOR""$i"
done
CP="$CP""$CP_SEPARATOR""$LIQUIBASE_HOME/lib/"
for i in "$LIQUIBASE_HOME"/lib/*.jar; do
CP="$CP""$CP_SEPARATOR""$i"
done
fi
if [ -z "${JAVA_HOME}" ]; then
#JAVA_HOME not set, try to find a bundled version
if [ -d "${LIQUIBASE_HOME}/jre" ]; then
JAVA_HOME="$LIQUIBASE_HOME/jre"
elif [ -d "${LIQUIBASE_HOME}/.install4j/jre.bundle/Contents/Home" ]; then
JAVA_HOME="${LIQUIBASE_HOME}/.install4j/jre.bundle/Contents/Home"
fi
fi
if [ -z "${JAVA_HOME}" ]; then
JAVA_PATH="$(which java)"
if [ -z "${JAVA_PATH}" ]; then
echo "Cannot find java in your path. Install java or use the JAVA_HOME environment variable"
fi
else
#Use path in JAVA_HOME
JAVA_PATH="${JAVA_HOME}/bin/java"
fi
# add any JVM options here
JAVA_OPTS="${JAVA_OPTS-}"
"${JAVA_PATH}" -cp "$CP" $JAVA_OPTS liquibase.integration.commandline.LiquibaseCommandLine ${1+"$@"}

37
liquibase-4.9.1/liquibase.bat Normal file
View File

@ -0,0 +1,37 @@
@echo off
if "%OS%" == "Windows_NT" setlocal
setlocal enabledelayedexpansion
rem %~dp0 is expanded pathname of the current script under NT
set LIQUIBASE_HOME="%~dp0"
set CP=.
for /R %LIQUIBASE_HOME% %%f in (liquibase*.jar) do set CP=!CP!;%%f
for /R liquibase_libs %%f in (*.jar) do set CP=!CP!;%%f
for /R %LIQUIBASE_HOME%\lib %%f in (*.jar) do set CP=!CP!;%%f
rem remove quotes around LIQUIBASE_HOME
set LIQUIBASE_HOME=%LIQUIBASE_HOME:"=%
rem remove quotes around JAVA_HOME if set
if NOT "%JAVA_HOME%" == "" set JAVA_HOME=%JAVA_HOME:"=%
rem set JAVA_HOME to local jre dir if not set
if exist "%LIQUIBASE_HOME%\jre" if "%JAVA_HOME%"=="" (
set JAVA_HOME=%LIQUIBASE_HOME%\jre
)
rem add the lib directory itself to the classpath
set CP=!CP!;!LIQUIBASE_HOME!lib
rem special characters may be lost
setlocal DISABLEDELAYEDEXPANSION
IF NOT DEFINED JAVA_OPTS set JAVA_OPTS=
set JAVA_PATH=java
if NOT "%JAVA_HOME%" == "" set JAVA_PATH=%JAVA_HOME%\bin\java
"%JAVA_PATH%" -cp "%CP%" %JAVA_OPTS% liquibase.integration.commandline.LiquibaseCommandLine %*

BIN
liquibase-4.9.1/liquibase.jar Normal file
View File

Binary file not shown.

5
liquibase-4.9.1/liquibase.properties Normal file
View File

@ -0,0 +1,5 @@
url=jdbc:postgresql://localhost:5432/liquibase_example
username=postgres
password=121314Ma
changeLogFile=db/changelog/db.changelog-master.xml
liquibase.hub.mode=off

23
pom.xml
View File

@ -5,17 +5,25 @@
<parent> <parent>
<groupId>org.springframework.boot</groupId> <groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId> <artifactId>spring-boot-starter-parent</artifactId>
<version>2.4.3</version> <version>2.6.7</version>
<relativePath/> <!-- lookup parent from repository --> <relativePath/> <!-- lookup parent from repository -->
</parent> </parent>
<groupId>org.sadtech.example</groupId>
<groupId>dev.struchkov.example</groupId>
<artifactId>liquibase</artifactId> <artifactId>liquibase</artifactId>
<version>0.0.1-SNAPSHOT</version> <version>0.0.1-SNAPSHOT</version>
<name>liquibase</name>
<description>Demo project for Spring Boot</description> <name>Liquibase Examples</name>
<description>Demo project using liquibase</description>
<properties> <properties>
<java.version>1.8</java.version> <java.version>17</java.version>
<maven.compiler.source>${java.version}</maven.compiler.source>
<maven.compiler.target>${java.version}</maven.compiler.target>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
</properties> </properties>
<dependencies> <dependencies>
<dependency> <dependency>
<groupId>org.springframework.boot</groupId> <groupId>org.springframework.boot</groupId>
@ -45,11 +53,6 @@
<artifactId>lombok</artifactId> <artifactId>lombok</artifactId>
<optional>true</optional> <optional>true</optional>
</dependency> </dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
</dependencies> </dependencies>
<build> <build>

2
src/main/resources/application.yaml → src/main/resources/application.yml
View File

@ -3,6 +3,6 @@ spring:
url: jdbc:postgresql://localhost:5432/liquibase_example url: jdbc:postgresql://localhost:5432/liquibase_example
username: postgres username: postgres
driver-class-name: org.postgresql.Driver driver-class-name: org.postgresql.Driver
password: 121314Ma password:
liquibase: liquibase:
change-log: classpath:db/changelog/db.changelog-master.xml change-log: classpath:db/changelog/db.changelog-master.xml

49
src/main/resources/db/changelog/db.changelog-master.xml
View File

@ -1,49 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog <databaseChangeLog
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.liquibase.org/xml/ns/dbchangelog" xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.1.xsd"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="create-table-person" author="uPagge"> <include file="v.1.0.0/cumulative-changelog.xml" relativeToChangelogFile="true"/>
<createTable tableName="person"> <include file="v.2.0.0/cumulative-changelog.xml" relativeToChangelogFile="true"/>
<column name="id" type="int" autoIncrement="true">
<constraints nullable="false" primaryKey="true"/>
</column>
<column name="name" type="varchar(64)"/>
<column name="telegram_id" type="int">
<constraints unique="true"/>
</column>
</createTable>
</changeSet>
<changeSet id="add-new-column-address" author="uPagge">
<addColumn tableName="person">
<column name="address" type="varchar(300)"/>
</addColumn>
</changeSet>
<changeSet id="create-table-book" author="uPagge">
<createTable tableName="book">
<column name="id" type="int" autoIncrement="true">
<constraints nullable="false" primaryKey="true"/>
</column>
<column name="name" type="varchar(64)"/>
<column name="author_id" type="int"/>
</createTable>
<addForeignKeyConstraint baseTableName="book" baseColumnNames="author_id"
constraintName="book_author_id_person_id"
referencedTableName="person" referencedColumnNames="id" onUpdate="CASCADE"/>
</changeSet>
<changeSet id="create-view-book-author" author="uPagge">
<createView viewName="author_and_book">
SELECT p.id as person_id,
p.name as person_name,
b.id as book_id,
b.name as book_name
FROM person p
LEFT JOIN book b on p.id = b.author_id
</createView>
</changeSet>
</databaseChangeLog> </databaseChangeLog>

34
src/main/resources/db/changelog/v.1.0.0/create-table.xml Normal file
View File

@ -0,0 +1,34 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="create-table-person" author="uPagge">
<createTable tableName="person">
<column name="id" type="int" autoIncrement="true">
<constraints nullable="false" primaryKey="true"/>
</column>
<column name="first_name" type="varchar(64)"/>
</createTable>
</changeSet>
<changeSet id="add-new-column-address" author="uPagge">
<addColumn tableName="person">
<column name="address" type="varchar(300)"/>
</addColumn>
</changeSet>
<changeSet id="create-table-book" author="uPagge">
<createTable tableName="book">
<column name="id" type="int" autoIncrement="true">
<constraints nullable="false" primaryKey="true"/>
</column>
<column name="name" type="varchar(64)"/>
<column name="author_id" type="int">
<constraints foreignKeyName="book_author_id_person_id" references="person(id)"/>
</column>
</createTable>
</changeSet>
</databaseChangeLog>

13
src/main/resources/db/changelog/v.1.0.0/cumulative-changelog.xml Normal file
View File

@ -0,0 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="add-tag-1.0.0" author="uPagge">
<tagDatabase tag="v.1.0.0"/>
</changeSet>
<include file="create-table.xml" relativeToChangelogFile="true"/>
</databaseChangeLog>

54
src/main/resources/db/changelog/v.2.0.0/create-table-hero.xml Normal file
View File

@ -0,0 +1,54 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="create-table-hero" author="uPagge">
<createTable tableName="hero">
<column name="id" type="int" autoIncrement="true">
<constraints nullable="false" primaryKey="true"/>
</column>
<column name="book_id" type="int">
<constraints nullable="false"/>
</column>
<column name="name" type="varchar(64)">
<constraints nullable="false"/>
</column>
</createTable>
</changeSet>
<changeSet id="create-fk" author="uPagge">
<addForeignKeyConstraint baseTableName="hero" baseColumnNames="book_id"
constraintName="hero_book_id"
referencedTableName="book" referencedColumnNames="id"
deleteCascade="true"/>
</changeSet>
<changeSet id="insert-into" author="uPagge">
<insert tableName="person">
<column name="first_name" value="Александр"/>
</insert>
<insert tableName="book">
<column name="name" value="Капитанская дочка"/>
<column name="author_id" value="1"/>
</insert>
<insert tableName="hero">
<column name="name" value="Савельич"/>
<column name="book_id" value="1"/>
</insert>
<rollback>
<delete tableName="hero">
<where>name = 'Савельич'</where>
</delete>
<delete tableName="book">
<where>name = 'Капитанская дочка'</where>
</delete>
<delete tableName="person">
<where>first_name = 'Александр'</where>
</delete>
</rollback>
</changeSet>
</databaseChangeLog>

13
src/main/resources/db/changelog/v.2.0.0/cumulative-changelog.xml Normal file
View File

@ -0,0 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.6.xsd">
<changeSet id="add-tag-2.0.0" author="uPagge">
<tagDatabase tag="v.2.0.0"/>
</changeSet>
<include file="create-table-hero.xml" relativeToChangelogFile="true"/>
</databaseChangeLog>