Differences between 0.2 and 0.3 - juxt/joplin GitHub Wiki
Migrator differences
-
:sqlmigrator files can now be either.sqlor.edn. See here for details. -
.sqlfiles now needs a marker--;;between different SQL statements in the same file. For more details see here. Please note that not all databases require this, for instance PSQL seems to be fine without. -
For
:jdbcmigrators a newer version of org.clojure/java.jdbc is used, and many functions has been moved to theclojure.java.jdbc.deprecatednamespace.
Joplin differences
-
Joplin configuration is no longer located in the
project.cljfile. Instead your code is responsible for providing the Joplin configuration map. See the example project on how to do this. Configuration map, loading configuration. -
The joplin leiningen plugin has been removed, similar functionality can be achieved using lein aliases. See the example project for details.
-
The
reset-dbmultimethod is removed. -
The
rollback-dbmultimethod now takes on more required argument (a number of a string of the ID to rollback to) -
The
create-migrationmultimethod now takes on more required argument (the name of the migration). -
For
:sql/:jdbcmigrators, the name of the migration table can now be set with the:migrations-tablekey in the :databases map. -
Joplin now supports specifying ragtimes conflict strategies when migrating.
Ragtime differences
Joplin 0.3 depends on ragtime 0.5, which contains some breaking changes.
- The main protocol that describes a datastore is now called
ragtime.protocols/DataStore(wasragtime.core/Migratable).