Packages

eventstore

0.11.0
1.4.8 1.4.7 1.4.6 1.4.4 1.4.3 1.4.2 1.4.1 1.4.0 1.3.2 1.3.1 1.3.0 1.2.3 1.2.2 1.2.1 1.2.0 1.1.0 1.0.3 1.0.2 1.0.1 1.0.0 1.0.0-rc.0 0.17.0 0.16.2 0.16.1 0.16.0 0.15.1 0.15.0 0.14.0 0.14.0-rc.0 0.13.2 0.13.1 0.13.0 0.12.1 0.12.0 0.11.0 0.11.0-rc.0 0.10.1 0.10.0 0.9.0 0.8.1 0.8.0 0.7.4 0.7.3 0.7.2 0.7.1 0.7.0 0.6.2 0.6.1 0.6.0 0.5.2 0.5.1 0.5.0 0.4.3 0.4.2 0.4.1 0.4.0 0.3.0 0.2.1 0.2.0 0.1.0 0.0.5 0.0.4 0.0.3 0.0.2 0.0.1

Event store using PostgreSQL for persistence.

HexDocs

Current section

Files

Jump to
Readme
65 Versions
6 Dependencies
8 Dependants
Files
Activity
eventstore guides Upgrades.md
Raw

guides/Upgrades.md 

# Upgrading an EventStore



The [CHANGELOG](https://github.com/slashdotdash/eventstore/blob/master/CHANGELOG.md) is used to indicate when a schema migration is required for a given version of the EventStore.



The [migration scripts](https://github.com/slashdotdash/eventstore/tree/master/scripts/upgrades) are provided for upgrading an existing EventStore. Creating an EventStore, using the `mix event_store.create` task, will always use the latest database schema.



You must stop the `:eventstore` application to apply an upgrade. It is *always* worth taking a full backup of the EventStore database before applying an upgrade.



Since v0.10.0 a `schema_migrations` table has been used to record when each migration took place.