|
DataNucleus AccessPlatform 2.0 builds on the 1.1 release, adding on more features around
the currently supported datastores and supporting new datastores.
All releases are checked regularly against the JDO/JPA TCKs, meaning that DataNucleus has
reached a level of stability in terms of functionality.
Occasionally, due to unknown bugs, or due to new functionality being introduced we need to
change some aspects of DataNucleus. As a result sometimes users will have to make some
changes to move between versions of DataNucleus. We aim to keep this to a minimum.
Migrating from AccessPlatform 2.0.1 to 2.0.2 will require the following changes
-
Excel support has been upgraded to use Apache POI 3.5+
Migrating from AccessPlatform 2.0.0 Release to 2.0.1 will require no changes.
Migrating from AccessPlatform 2.0.0 M4 to 2.0.0 Release will require no changes.
Migrating from AccessPlatform 2.0.0 M3 to 2.0.0 M4 will require the following changes.
-
Some property names have changed on the Maven2 plugin relating to location
of mapping files and classes. See the docs
-
The enhancer option "-persistenceUnit" is now "-pu" for consistency with the JDO API,
and since much shorter. The option --persistenceUnit still works
-
The RDBMS SchemaTool option "-persistenceUnit" is now "-pu" for consistency with the
enhancer and since much shorter. The option --persistenceUnit still works
Migrating from AccessPlatform 2.0.0 M2 to 2.0.0 M3 will require the following changes.
-
L2 cache property
datanucleus.cache.level2.type
now defaults to
soft
-
L1 cache property
datanucleus.cache.level1.type
now defaults to
soft
Migrating from AccessPlatform 2.0.0 M1 to 2.0.0 M2 will require the following changes.
-
Persistence property
datanucleus.rdbms.sql.allowAllSQLStatements
is renamed
to
datanucleus.query.sql.allowAll
Migrating from AccessPlatform 1.1.x to 2.0.0 M1 will require the following changes.
-
L1 cache property
datanucleus.cache.level1.type
value
hard
is
renamed
strong
-
Query Cache is now split into generic compilation, datastore compilation and
results caches. As a result
datanucleus.cache.query.type
is replaced by
datanucleus.cache.queryCompilation.type
,
datanucleus.cache.queryCompilationDatastore.type
and
datanucleus.cache.queryResults.type
-
Renamed the values for persistence property
datanucleus.identifierFactory
to be
datanucleus
(was "jpox"),
datanucleus2
(was "jpox2")
and
jpox
(was "jpoxCompatibility"). Changed the default to
datanucleus2
from
datanucleus
, so if not setting your column names
bear this in mind since the names are different obviously
-
Changed the default auto-start mechanism to be "None" for all datastores. Set it
via the persistence property
datanucleus.autoStartMechanism
where needed
-
Changed the default non-transactional read/write settings to "true" for JDO (were
already true for JPA)
-
Some refactoring has been done internally so if relying on DataNucleus APIs you
should check against SVN for changes.
|
|
