Liquibase 3.10.1 is a bugfix release

Changes

• GH PR#913 - [CORE-3471] Fixed NPE in LiquibaseUtil when MANIFEST.MF doesn't contain Bundle-Version or Build-Time
• GH PR#917 - [Core 3463] Fix for validateX attributes of constraintsConfig
• GH PR#919 - Fixed issued with bundling in shaded jars
• GH PR#941 - [CORE-3520] Add support for ALWAYS generation type with PostgreSQL auto-increment column.
• GH PR#946 - [CORE-3524] Prevent auto-increment column silently failing on Oracle.
• GH PR#949 - [CORE-3526] TABLE is a reserved keyword in H2database since 1.4.197
• GH PR#963 - [CORE-3556] No default values for changes' properties
• GH PR#965 - [CORE-3558] Unique constraint name is ignored when using the addColumn change
• GH PR#970 - Fix Java 1.9+ versions require jaxb as separate dependency
• GH PR#971 - Add Class-Path entry to the manifest file to simplify command line execution
• GH PR#975 - NULL date value in prepared statement requires type in MSSQL
• GH PR#986 - XMLSerializer: Correct Map value serialization
• GH PR#993 - Improve ChangeFactory initialization time
• GH Issue#1035 - Change how Liquibase produces debug logs
• GH Issue#1051 - Update liquibase-core.jar to exclude ServiceLoader files
• GH PR#1053 - Update liquibase_autocomplete.shape
• GH PR#1059 - Allow multiple column unique constraints on table creation.
• GH Issue#1069 - Patch Liquibase Runner plugin for Jenkins
• GH Issue#1070 - Enable --help without databse connection
• GH PR#1082 - Correct include bash script
• GH PR#1096 - Fix sequence statement generation for PostgreSQL <= 9.4
• GH Issue#1104 - Fix maven-liquibase offline diff to prevent errors
• GH Issue#1113 - Fix schema name using "--defaultSchemaName" on a non-default schema
• GH PR#1120 - LiquibaseServletListener.contextInitialized() improved with Embedded Derby
• GH Issue#1220 - Fix how JAVA_HOME env variable is handled

This release merges many community-contributed pull requests. Thanks to everyone who helps make the Liquibase community strong!

Improvements and Bugfixes

In this second beta for the new major version release, we

• Updated of all of the extensions to take advantage of Liquibase 4.0
• Included a compatibility layer for any pre-4.0 community extensions
• Stopped including root filesystem in default CLI search paths
• Fix for --logLevel=debug/fine

How to be a Beta Tester

Please check out https://liquibase.jira.com/wiki/spaces/LB/pages/1274904689/Liquibase+Beta for details on how to get involved with the Liquibase 4.0beta2 test plan. Testing database extensions is the focus for Beta 2.

The goal is to uncover, document, and share all the issues that keep you from working how you want to work with Liquibase. Please test your setup and document any problems as new GitHub Issues or GitHub Code Contributions.

Liquibase 3.10.0 offers SQL Plus integration, Custom Executor extensibility, Complementary Bash script

SQL Plus Integration and the new "runWith" attribute

There are occasions when the Liquibase in-built JDBC connector has trouble processing highly-specialized or variable-rich SQL, and a more purpose-built tool, like SQL Plus or other executor, is required.

For Liquibase Open Source and Pro users, we are introducing an optional changeset attribute, called runWith="<executor>" which allows you to specify an “executor” to run your SQL. This new capability works with changesets in Formatted SQL, XML, JSON or YAML changelogs which call inline SQL or sqlFile tagged changesets. For Pro users, there is also a new liquibase.sqlplus.conf file, which lives alongside your liquibase.properties or POM file, where you can optionally specify some useful key-value pairs for configuring your executor.

As a Liquibase Pro user, employ the new SQLPlus integration by simply adding runWith="sqlplus" to a changeset, and have SQL Plus in your PATH (or configure it in the accompanying liquibase.sqlplus.conf file). It’s now that easy to run your complex or specialized SQL changesets with SQL Plus.

Integrate your own executor

As exciting, and true to open-source and open-extensibility, Liquibase Open Source users can now write their own classes to integrate their own executor. Say, for example, you need an encrypted JDBC tool, which you want to call as “ejdbc” from your changeset? Simply follow the included example so you can take advantage of this new feature:

• Write and configure the classes to call your tool
• Add runWith="ejdbc" to select changesets to process them with your custom executor

New Auto-complete Bash Script

In the Liquibase 3.10 release, you will also find a new bash script for MacOS / and Git Bash for Windows users called .liquibase-completion-mac.bash. This script adds some ease of use to the CLI, including auto-complete of commands and and auto-rollout of parameters. This is a single bash script that will not affect any core Liquibase code, and can live alongside the existing bash script which has and will continue to ship with Liquibase.

Liquibase 3.9.0 extends diff command with Pro capability

Liquibase Pro can help you automate drift detection at scale in your database schemas with a new structured and machine readable diff output as json. This additional capability is an Pro extension to the existing community command "diff", and is invoked with a new --format option
$> liquibase diff --format=json

This outputs a JSON structured object listing the differences between two databases (as configured in your liquibase.properties or Maven POM file under the "url" and "referenceUrl" keys.) By default, the result is output to STDOUT, which provides you with maximum flexibility to pipe the result into other tools or a processing pipeline. You can also have the output delivered to a file, using the "--outputFile=<filename>" global parameter, as in
$> liquibase --outputFile=myfile.json diff --format=json

Whether you choose STDOUT or a collection of files, you can then process this data to generate reports, to trigger actions, from alerts to diffChangeLogs, to updates, or whatever make sense for how you use Liquibase.

😎 Download Liquibase 4.0.0-beta1 in the Assets section at the bottom of this release note. 😎

Improvements and Bugfixes

In this major new version release, we have integrated dozens of community Pull Requests, addressing well over 100 bugs, in addition to the dozens of updates to the 3.8.x branches.

How to be a Beta Tester

Please check out https://liquibase.jira.com/wiki/spaces/LB/pages/1274904689/Liquibase+Beta for details on how to get involved with the Liquibase 4.0beta1 test plan, including code and integrations tested, not tested, and not ready for test, yet.

The underlying goal of Beta testing is to uncover, document, and share all the issues that keep you from working how you want to work with Liquibase. Please test your setup and document any problems as new GitHub Issues or GitHub Code Contributions.

What We Tested

This Major version Beta release comes with the risks of all Beta software! We have tested dozens of PRs across multiple environments interacting with multiple databases, but we cannot test all the wildly diverse ways the community uses Liquibase. But you can! In this Beta we are counting on valuable community members — like you — to put this Beta through your paces and then to file (and possibly fix) any issues which you encounter in your specific setup and use cases.

We covered the following broad categories:

1. Where Liquibase Writes Output
2. How Liquibase Finds Files
3. How Liquibase Works in Integrations
4. How Liquibase Interacts with the Database
5. How Liquibase Pro interacts with the Database

Highlighted Changes and Bug Fixes

We made two major/breaking changes to the Liquibase Library API. These will affect anyone using extensions, but do NOT impact the main Liquibase functionality:

• Extension classes are now loaded via the java.util.ServiceLoader system rather than the custom class finding logic we had before
• Logging is now based on java.util.Logging with a cleaned up API

In addition to these two major changes, the following changes have been incorporated as well:

• Fixes to ConstraintsConfig
• ignoreLines command in formatted sql log
• postgresql >= 10: use identity columns for autoincrement
• Using proxy user for Oracle Connections
• Capture table remarks on mysql
• Add PERIOD to reserved words for MariaDB
• Don't require columnDataType on H2 for addNotNullConstraint
• Do not remove trailing /'s of comments like /* dsds */
• Require type xsd:string to where element of update element/files
• runOnChange change set runs every time even if there wasn't changed
• Indexes with DESC sorting are not created for PostgreSQL
• Added Ingress support
• Support boolean in firebird 3.0
• Change Log Parameters from Environment Variable
• Adds clearCheckSums property in spring integration
• Oracle datatype translation changes
• Implement Sequence Support for MariaDB
• Cleanup checksum classes
• Fix Turkish uppercase column keys bug
• Generate diff with onDelete and onUpdate
• PrimaryKeySnapshotGenerator throws NPE for SQLite
• Handle java.sql.Time when setting prepared statement parameter values in CSV filese
• DB2 LUW supports boolean data type column from version 11.1.1.1
• Offline history support not correctly closing files
• Use computeIfAbsent to avoid Liquibase concurrency issues
• Firebird does not support RESTRICT option on Foreign Keys
• Liquibase was ignoring DatabaseFunction value and processing only SequenceNextValueFunction when creating tables and generating column default value.
• Restore usage of DatabaseList.definitionMatches to match the dbms tag against the database type
• DEPLOYMENT_ID column header not included in offline updateSql CSV
• Can't set some parameters for snapshot & generate changelog
• UUID type handling improvements
• Correctly close yaml file in generateChagneLog
• Adding restricted words for MSSQL Server Database
• Getting a java.io.FileNotFoundException using Liquibase with Spring reactive web
• FileSystemResourceAccessor fails with non-hierarchical URLS on classpath
• fix oracle date literal without millis
• fix nullPointerException when migrating RedShift
• Prints the SQL error code on Exception
• Fixed SetColumnRemarks for mysql
• Allow “NOW” and “Today” literal capabilities in CSV filese
• Add ability to disable running of Liquibase via CDILiquibaseConfig

Bug Fixes & Improvements

For both Liquibase Open Source and Pro users, the following bugs were fixed in version 3.8.9:

• Fixed an issue with how Liquibase handles SMALLINT on PostgreSQL when generating a changelog.
• Improved generateChangeLog command to assume a diffTypes that includes "data" when the dataOutputDirectory parameter is used. Most users looking to export data as part of generateChangeLog can now simply use the dataOuputDirectory parameter without needing to specify diffTypes.
• The --schemas parameter now works on either side of the snapshot command.
• Enabled generatechangelog in PostgreSQL to correctly order create, function, and trigger statements.
• Improved the use of dblink objects when using diff command.

Liquibase 3.8.8 Released, Provides Minor Bug Fixes

Bug Fixes

For both Liquibase Open Source and Liquibase Pro users, the following bugs were fixed in version 3.8.8:

• rollbackOneChangeSetSQL now works correctly with the Liquibase Maven plugin.
• Liquibase Pro no longer generates procedural code with incorrect SQL syntax when running generateChangeLog against a MySQL database.

Liquibase 3.8.7 Overview

Liquibase 3.8.7 Extends Targeted Rollbacks Capabilities for Liquibase Pro

We are excited to announce with the release of Liquibase 3.8.7, Liquibase Pro users now have additional targeted rollback capabilities with two brand new commands! The creation of the rollbackOneUpdate command allows users to rollback their last update, or target any previous update with a --deploymentId parameter, and our new rollbackOneUpdateSQL command allows you view the SQL your rollbackOneUpdate command would produce prior to deploying it. That way, you can ensure you don't encounter any unintended consequences before rolling back.

Each one of these commands come with their own --help to give you friendly command-specific assistance when you need it most. Just type liquibase rollbackOneUpdate --help or liquibase rollbackOneUpdateSQL --help to find what you need.

To also help you navigate the Targeted Rollback waters, our fantastic engineers have created a brand new command available to both Liquibase Open Source and Pro users, we call this command history. The history command lists out all of your deploymentIds and all changeSets associated with each deploymentId so you can inspect a group of changes to ensure they have been applied to the database. Just type liquibase history into your command line to see it in action. Don't forget, you can also use a --outputFile parameter to write this information to a text file!

Bug Fixes

Liquibase 3.8.7 also continues our initiative to make Liquibase bigger, badder, and even better than before. For both Liquibase Open Source and Liquibase Pro users, the following bugs were fixed in version 3.8.7:

• --help was improved to include missing commands and correct information.
• CompositeClassLoader does not implement getResource(String)

Liquibase 3.8.6 Overview

Windows and MacOS installers

In addition to the existing zip/tar distributions, there are now liquibase-installer.exe and liquibase-installer.dmg graphical installers.

These installers include everything you need to run Liquibase (including Java) to make getting started easier than ever.

GETTING_STARTED.txt

Regardless of how you install Liquibase, there is now a GETTING_STARTED.txt file that points you to some sample projects to start trying Liquibase as quickly as possible.

Targeted Rollbacks for Liquibase Pro with 'rollbackOneChangeset' command

You asked, and we listened! With the release of Liquibase 3.8.6, Liquibase Pro users will now have additional rollback capabilities with Targeted Rollback, a powerful new feature that allows you to target one changeSet to rollback, without affecting all the other changeSets which followed it. Think "git cherry pick" for rollbacks.

We even added a helper command "rollbackOneChangsetSQL", which will show you the SQL that will be used in the rollbackOneChangeset command.

You can now also receive command specific help for Targeted Rollback by typing in either
liquibase rollbackOneChangeSet --help or
liquibase rollbackOneChangeSetSql --help.

Bug Fixes

Liquibase 3.8.6 also continues our initiative to re-engage with our users by bringing new bug fixes to our Liquibase platform. For both Liquibase Open Source and Liquibase Pro users, the following bugs were fixed in version 3.8.6:

• excludeObjects& includeObjects parameters now works correctly when running diff.
• dataOutputDirectory parameter will now specify statement csv files appropriately.
• Updated default MySql driver to com.mysql.cj.jdbc.Driver

Liquibase 3.8.5

We've fixed a number of issues with this release.

Bug Fixes

For both Liquibase Open Source and Liquibase Pro users, the following bugs were fixed in version 3.8.5:

• Fixes issue in which Liquibase did not add DESC to an id column
• CLI once again accepts sqlFile, delimiter, rollbackScript, and outputSchemaAs arguments
• Fixes Stored Procedure whitespace impacting update calls
• Fixes generateChangelog failure when there are missing NOT NULL constraints
• Fixes updateSQL, which was not including schemaName for package bodies
• Fixes bug in which Liquibase was not always capturing create package body while generating changeLog
• Liquibase CLI now gives a more useful error message when an invalid character is passed to a command
• Fixes an MSSQL issue, which threw an exception when doing diff/diffChangeLog between offline connections (such as when snapshotting json files)
• Fixes an MSSQL issue, which incorrectly generated datetime data type column when using diff & diffChangeLog Liquibase Maven plugin fails while executing/using "diff" and "generateChangeLog" with PostgreSQL)

Liquibase 3.8.4 improves support for Liquibase in Spring Boot with Java 9+

For both Liquibase Open Source and Liquibase Pro users, the following bugs were fixed in version 3.8.4:

• Fixed a 'Class not Found' exception error when using Java +9.
• Fixed a 'Cannot Use Default Schema Name' error when users diff against an SQL Server snapshot file.
• Fixed an 'Unexpected type: java.util.Date' error when using a defaultValueDate attribute in a YAML changelog.

Liquibase 3.8.3 improves support for Liquibase-Maven plugin and Java 9+

It is true, sometimes things break. Sorry! However, with the release of Liquibase 3.8.3, users of both Liquibase Open Source and Liquibase Pro can enjoy improved Liquibase-Maven plugin experiences, especially when using Java 9+.

Bug Fixes

For both Liquibase Open Source and Liquibase Pro users, the following bugs were fixed in version 3.8.3:

• Liquibase-Maven plugin now works with Java 9+.
• Expired license messages should be far less verbose and excitable.

LIQUIBASE 3.8.2

With the release of Liquibase 3.8.2, Liquibase Pro users, along with support, can now enjoy even more database change control with the capability to capture and export Stored Logic objects, such as triggers, procedures, functions, and more.

WHAT’S NEW IN VERSION 3.8.2

Liquibase Pro Only: Stored Logic Objects are now captured for Postgres and DB2, so users can reverse engineer database changes, and capture triggers, functions, procedures, and more using generateChangeLog, snapshot, diff, and diffChangeLog commands.

Liquibase Pro Only: Stored logic objects will now export into local directories and files.

BUG FIXES

For both Liquibase Open Source and Liquibase Pro users, the following bugs were fixed in version 3.8.2:

• Using generateChangeLog/diffChangeLog to generate formatted sql changelogs now works with Liquibase Pro's stored logic support
• CDI-related classes moved back out of the main liquibase jar into an optional jar
• Fixed issue with indexes backing foreign keys not always being caputured in diffChangeLog/generateChangeLog
• Fixed issue with diffChangeLog/generateChangeLog generating primary keys when column order doesn't match the table's column order

• [PRO] Oracle and SQL Server users can now reverse engineer database changes for stored logic such as triggers, functions & procedures using generateChangeLog, snapshot, diff, and diffChangeLog commands. 

• Bugfixes in logging and outputFile
• Bugfixes in SQL Server index snapshot

[CORE-2379] - Project.version set to 3.3.4-SNAPSHOT in 3.3.4 final

[CORE-2360] - Maven - Skip is active by default
[CORE-2199] - Liquibase adds a semicolon after a stored proc definition making the stored proc unusable
[CORE-2344] - Unknown host exception on OS RHEL 6.5
[CORE-2346] - IncludeAll does not work when runing liquibase from inside a jar
[CORE-2357] - alterSequence does not work as expected when you need to change the cache size
[CORE-2366] - Derby Network server works with command line but not with maven "Liquibase skipped due to maven configuration"
[CORE-2368] - No SQL outputted for change

[CORE-1768] - Oracle dropAll fails on spatial tables and sequences
[CORE-1840] - Liquibase fails when run on a computer that can't connect to the internet
[CORE-1857] - Wrong column size detection on varchar2 fields with char as datatype
[CORE-1866] - Filtering changelog list by includeAll tag is not working
[CORE-1943] - Handle Error: InetAddress.getLocalHost().getHostName() UnknownHostException results in NoClassDefFoundError
[CORE-1958] - Column type of "TIMESTAMP(6)" under MySql converted to TIMESTAMP dropping fractional seconds
[CORE-1967] - includeAll uses full file path for sql changelogs
[CORE-2023] - Problem using includeAll with SpringLiquibase
[CORE-2126] - Postgres 9.3 - Drop table With Cascade - Not Supported
[CORE-2156] - Resource loader can't load changelog file
[CORE-2186] - AbstractResourceAccessor#convertToPath(String, String) fails for processing includeAll from Classpath
[CORE-2192] - NoSuchMethodException when generating offline Oracle migration script
[CORE-2199] - Liquibase adds a semicolon after a stored proc definition making the stored proc unusable
[CORE-2202] - liquibase.should.run inverted boolean
[CORE-2204] - valueNumeric not being set when using prepared statements
[CORE-2206] - diffChangeLog with JPA-annotated entities causes ConcurrentModificationException
[CORE-2208] - Typo in message
[CORE-2210] - java.lang.NullPointerException when file is empty
[CORE-2214] - When inserting string value starting and ending with apostrophes (quotes) the value is not quoted in the generated SQL
[CORE-2218] - Regression on modifyDataType : VARCHAR2 was supported on 3.2...and fails on 3.3
[CORE-2239] - Remarks attribute in renameColumn causes parse error
[CORE-2240] - setDropFirst(true) still broken on empty database
[CORE-2262] - 3.3.2 ant task dies on NPE in ChangeLogParameters
[CORE-2263] - Index Snapshot - doesn't include upper cased name indexes when db is NOT case sensitive
[CORE-2274] - Ant Upade Task does not consider changeLogFile correctly if it is contained in a JAR
[CORE-2279] - Rollback fails in MS SQL 2008 using liquibase 3.3.2
[CORE-2284] - Creating a DatabaseChangeLog() results in NPE
[CORE-2290] - Liquibase gives different results from Ant and the command line
[CORE-2301] - Regression from 3.2.3 in mssql 2000 unsupported usage of varchar(max) and sys.extenden_properties
[CORE-2304] - Autoincrement on type INT4 fails
[CORE-2310] - IncludeAll Fails with Unknown Reason Error
[CORE-2315] - NPE in CommandlineResourceAccessor
[CORE-2325] - Liquibase - New versions break DB create
[CORE-2329] - Escaped reserved keywords in HSQL are stored in lower case instead of upper case.
[CORE-2330] - includeAll uses full file path with includeAll
[CORE-2261] - UpdateSQL needs to append a "/" to the end of createProcedure for Oracle
[CORE-2287] - Improve support for Groovy-based tests in Eclipse
[CORE-2296] - Upgrade Groovy and Spock to maintained versions
[CORE-2318] - Add support for converting BigDecimal objects to a SQL string via DataTypeFactory

• Support for ignoring objects in diffChangeLog and generateChangeLog
• Bugfixes
• [CORE-875] - Ignore tables for diffs and generateChangelog
• [CORE-1877] - SQLOutput prints endDelimiter regexes
• [CORE-2114] - AddAutoIncrement on Postgres does not work when changes are applied on a specific schema
• [CORE-2141] - handling dependencies and WAR as classpath
• [CORE-2166] - SpringLiquibase: includeAll within jar causes SetupException
• [CORE-2172] - dropPrimaryKey without constraint name on sql server doesn't honour schema information
• [CORE-2174] - Bad exception handling in OracleDatabase.setConnection
• [CORE-2180] - NPE with bad name
• [CORE-2182] - ClassLoader leak due to shutdown hooks

• IncludeAll bugfixes
• Performance improvements
• Datatype handling fixes
• Fix for JSON parsing
• Other bugfixes
• [CORE-1920] - SpringLiqubase includeAll is not including files
• [CORE-2009] - ClassCastException when executing a custom task change (AntClassLoader problem)
• [CORE-2097] - "mvn liquibase:futureRollbackSQL" asks for tag, count or date
• [CORE-2099] - SQLAnywhere support (Driver not capable)
• [CORE-2103] - changelogSchemaName/changelogCatalogName configuration options will not work on Oracle DB
• [CORE-2104] - ConcurrentModificationException iterating over System.getProperties().entrySet()
• [CORE-2105] - Maven profile performing dropAll and update on Oracle failing with an error on populated database.
• [CORE-2107] - LOWER() keyword fails on Postgres createIndex task
• [CORE-2108] - dropAll command trying to drop column on table that has already been dropped
• [CORE-2114] - AddAutoIncrement on Postgres does not work when changes are applied on a specific schema
• [CORE-2116] - Could not find implementation of liquibase.logging.Logger
• [CORE-2118] - Change default diffChangeLog/generateChangeLog objectQuotingStrategy back to LEGACY
• [CORE-2119] - Bad finally block in SpringLiquibase.afterPropertiesSet()
• [CORE-2120] - LoadUpdateData with value=NUMERIC quoting values
• [CORE-2121] - DB2: DiffChangeLog/GenerateChangeLog/DropAll sees alias column and tries to drop/add them
• [CORE-2127] - updateSQL creates duplicate DATABASECHANGELOGLOCK tables
• [CORE-2130] - setFetchSize to a negative value breaks Oracle JDBC Driver
• [CORE-2134] - ExecuteCommand won't run with no os attribute.
• [CORE-2136] - Mysql must quote PARTITION as a keyword
• [CORE-2137] - Special characters ( ) copied during generateChangelog on DB2/400
• [CORE-2139] - H2Database.supportsDropTableCascadeConstraints() returns false
• [CORE-2141] - handling dependencies and WAR as classpath
• [CORE-2142] - generateChangeLog not including all columns in a table
• [CORE-2146] - snakeyaml is pulled in as transitive dependency for using projects
• [CORE-2149] - Liquibase command line fails
• [CORE-2150] - On the 3.3.0-SNAPSHOT, liquibase --version returns 3.2.0
• [CORE-2153] - Liquibase 3.2.1 is no longer compatible with Oracle 9
• [CORE-2155] - diffTypes=data fails with java.sql.SQLException: Attribute value not valid (dataOutputDirectory attribute causes build to fail)
• [CORE-2156] - Resource loader can't load changelog file
• [CORE-2157] - SQLException if there are single quotes in ChangeSet
• [CORE-2159] - Datetime2 no longer used for MSSQL
• [CORE-2161] - includeAll relativeToChangelogFile="true" doesn't work
• [CORE-2164] - SpringLiquibase: includeAll within jar causes NullPointerException
• [CORE-2115] - Really slow when using fat jars
• [CORE-2125] - Make DatabaseChangeLog#include(String, boolean, ResourceAccessor) public
• [CORE-2148] - Build failure on jdk-1.8
• [CORE-2152] - Change logs in json format not processed by liquibase - parsing errors

• New "label" attribute on changeSet
• New empty and output change tags
• Support for clustered/nonclustered primary keys and indexes
• Saving of remarks in mysql and mssql
• Official RPM and DEB packages
• Refactoring/update of Ant integration
• [CORE-16] – Support for “nonclustered” primary keys in mssql
• [CORE-54] – Support System Properties in Maven Plugin
• [CORE-1528] – Installer for Liquibase
• [CORE-1598] – support for rename sequence
• [CORE-1914] – New Change function: output
• [CORE-1942] – Support for changeSet “labels”
• [CORE-549] – relativeToChangelogFile for loadData, loadUpdateData, sqlFile
• [CORE-1438] – createView should support having the entire view definition in the change body
• [CORE-1502] – CLONE – UpdateSQL needs to append a “/” to the end of createProcedure for Oracle
• [CORE-1654] – logicalFilePath support in formatted sql
• [CORE-1660] – “remarks” attribute is ignored in MSSQL
• [CORE-1932] – support for encrypted passwords / custom properties
• [CORE-1946] – Have a rpm package for liquibase (built with maven)
• [CORE-1963] – Ability to define full CREATE VIEW statement in change.
• [CORE-1990] – Preserve inline comments in view snapshots in mssql
• [CORE-2060] – Support liquibase.properties files with unknown properties
• [CORE-2061] – Improvements to Informix support
• [CORE-2062] – Add onlyUpdate flag to loadUpdateData
• [CORE-2064] – Use ignoreClassPathPrefix for rollback as well
• [CORE-2065] – Use DOUBLE PRECISION for DOUBLE with Firebird
• [CORE-2066] – Support for –outputFile in command line
• [CORE-2067] – Refactor Ant Task codebase
• [CORE-2068] – New liquibase.hostDescription property for additional details in the DATABASECHANGELOGLOCK table
• [CORE-2069] – Use prepared statement in change whenever a clob type is used
• [CORE-2072] – Do not include Oracle internal tables in snapshot/diff
• [CORE-870] – Postgres, in an ALTER TABLE ALTER COLUMN statement, sometimes needs USING clause
• [CORE-945] – Oracle : Temporary tables are created as regular tables
• [CORE-1463] – Views not generated correctly with generateChangelog
• [CORE-1556] – remarks attribute ignored for mysql
• [CORE-1723] – unable to update on DB2/400, version V6R1, on jt400-6.7.jar
• [CORE-1745] – afterColumn not working in MySQL
• [CORE-1774] – Autocommit not restored on close in SpringLiquibase
• [CORE-1882] – NullPointerException when MySQL foreign key points to an invalid table
• [CORE-1919] – SpringLiquibase fails when dropFirst is true
• [CORE-1922] – Sequence is not a reserved object name in HSQLDB
• [CORE-1925] – liquibase scripts can not represent clustered indexes
• [CORE-1937] – Oracle Float and VARCHAR precisions in changelog generated by generateChangeLog are incorrect
• [CORE-1952] – liquibase loadData does not properly load numeric field in boolean always as false
• [CORE-1956] – Double and float converted to FLOAT8(, 17) and FLOAT4(, 8) in PostgreSQL
• [CORE-1958] – Column type of “TIMESTAMP(6)” under MySql converted to TIMESTAMP dropping fractional seconds
• [CORE-1974] – dbchangelog-3.1.xsd missing
• [CORE-1977] – CreateSequence with cacheSize=0 failing on Oracle
• [CORE-1979] – MSSQL should not include parameters in SYSNAME data types
• [CORE-1981] – Parameters set in included file are no longer set in 3.2.0
• [CORE-1982] – Snapshot outputs defautlValueDate as defaultValueComputed on MSSQL for dates not in ISO format with a T in the middle
• [CORE-1986] – includeAll from changeLogs within a jar is not working
• [CORE-1988] – Reported size for Oracle NVARCHAR2 columns is wrong
• [CORE-1993] – Drop table with cascade is not supported by Sybase
• [CORE-1996] – addNotNullConstraint on h2 database has unexpected side effects
• [CORE-1997] – Bit changelog default value of 1 executed as 0
• [CORE-2002] – AbstractResourceAccessor generates path in a unpredictable way
• [CORE-2010] – Oracle data type SDO_GEOMETRY snapshotted as SDO_GEOMETRY(1)
• [CORE-2014] – applyToRollback property ignored when rollback changes are specified
• [CORE-2015] – DiffChangeLog writes to the wrong point in the file on windows if file uses \n not \r\n
• [CORE-2020] – Oracle default value current_timestamp converted to systimestamp
• [CORE-2021] – Column remarks not snapshotted in mssql
• [CORE-2026] – Oracle columns of type ANYDATA are snapshotted with a size
• [CORE-2028] – generateChangeLog on SQL Anywhere 11.0.1 throws DatabaseException Driver Not Capable
• [CORE-2032] – Snapshot incorrectly including clob/blob sizes on diff
• [CORE-2051] – Not quoting VIEW params with spaces when snapshotting
• [CORE-2054] – Add new “computed” column attribute to differentiate between an actual column name and a function as a column
• [CORE-2063] – Fix for H2 autoincrement “start with” and “increment by” syntax
• [CORE-2070] – dropAllForeignKeyConstraints does not work on Firebird databases
• [CORE-2075] – generateChangelog generates bad definition for TIME type
• [CORE-2080] – Liquibase “empty” change not present in XSD version 3.2
• [CORE-2081] – PrimaryKeyExists precondition without tableName is broken
• [CORE-2082] – Column snapshot on PostgreSQL does not include precision information for numeric data type
• [CORE-2087] – Executing against Oracle doesn’t respect liquibaseSchemaName or liquibaseCatalogName
• [CORE-2088] – outputDefaultSchema and outputDefaultCatalog command line parameters not respected
• [CORE-2093] – Error: Property ‘relativeToChangelogFile’ not found on object type liquibase.change.core.LoadDataChange
• [CORE-2094] – Liquibase.dropAll() should reset the lock service
• [CORE-2095] – Invalid generated changeset for mysql bit with defaultValue 0