Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Schema and Data Modifications in Liquibase

Schema and Data Modifications in Liquibase

The following steps outline how to modify a database schema and data using Liquibase and a database extension.

  1. With an XML editor, open your core-changelog-ext.xml, located in extensions\database\ext-schema-client\src\main\resources\liquibase
  2. Add new changesets to suit the needs of your new object or project. For details on possible database modifications you can make using changesets, see the Liquibase Changeset Refactoring manual.
  3. Save the modified core-changelog-ext.xml.
  4. Commit the changesets in core-changelog-ext.xml to your database by running the following command in ext-schema-client:
    mvn clean install liquibase:update
Warning:

Once a changeset has been committed, it must never be edited. Instead, commit additional changesets to counter-act your change.

Note: Populating an empty database with just the schema

You can use these steps to populate an empty database with just the database schema and no store data. However, if you intend to run the Commerce Engine web applications against your empty database, you'll need to set the COMMERCE/SYSTEM/ASSETS/assetLocation property, found in your database's tsettingdefinition table, to the absolute path where your Commerce Engine assets directory is located.