diff --git a/src/site/apt/migration/2.0-highlights.apt b/src/site/apt/migration/2.0-highlights.apt index 364473af4..b2bf16f83 100644 --- a/src/site/apt/migration/2.0-highlights.apt +++ b/src/site/apt/migration/2.0-highlights.apt @@ -156,7 +156,7 @@ public interface Tasklet { * Database Schema Changes - There are a couple of tidying up tasks and extensions to the data model in the meta data schema. We provide update scripts for anyone moving from 1.x to 2.0, so they shouldn't cause any problems, and will definitely make it easier to navigate and interact with the meta data. For those of you who are new to Spring Batch, some of the key benefits of the framework are the quality of service features like restartability and idempotence (process business data once and only once). We implement these features through shared state in a relational database (in most use cases), and the definition of the data model in this database has changed slightly in 2.0. + There are a couple of tidying up tasks and extensions to the data model in the meta data schema. Unfortunately we cannot provide update scripts for moving from 1.x to 2.0 because the differences cannot be bridged using plain SQL. Upgrading an existing database would require the old schema to be dumped and re-loaded with a custom job. Our recommendation is to leave the old data alone and start fresh with 2.0: the benefit is that the new APIs definitely make it easier to navigate and interact with the meta data. For those of you who are new to Spring Batch, some of the key benefits of the framework are the quality of service features like restartability and idempotence (process business data once and only once). We implement these features through shared state in a relational database (in most use cases), and the definition of the data model in this database has changed slightly in 2.0. The main changes are to do with the storage of <<>>, which used to be centralised in one table, even though the context can be associated either with a <<>> or a <<>>. The new model will be more popular with DBAs because it makes the relationships more transparent in the DDL. We also started storing the context values in JSON, to make them easier to read and track for human users (the context for a single entity is all stored in one row in a table, instead of many).