V.0.9.13 (beta) 2017/07/12 Kotlin Support
- Kotlin support (based on a new annotation processor)
- Started “object-kotlin”, a sub-project for Kotlin extensions (tiny yet, let us know your ideas!)
- BoxStoreBuilder: added maxReaders configuration
- Get multiple entities by their IDs via Box methods (see get/getMap(Iterable))
- ToOne and ToMany are now serializable (which does not imply serializing is a good idea)
- ObjectBox may now opt to construct entities using the no-args constructor if the all-args constructor is absent
- Prevents opening two BoxStores for the same DB file, which may have side effects that are hard to debug
- Various minor and internal improvements and fixes
- Fixed ToOne without an explicit target ID property
- Fixed type check of properties to allow ToMany (instead of List)
- Fixed @Convert in combination with List
- Fixed a race condition with cursor deletion when Java’s finalizer kicked in potentially resulting in a SIGSEGV
- Fixed a leak with potentially occurring with indexes
V0.9.12 (beta) 2017/05/08 ToMany class
- Update 2017/05/19: We just released 0.9.12.1 for the Gradle plugin (only), which fixes two problems with parsing of to-many relations.
- Added the new list type ToMany which represents a to-many relation. A ToMany object will be automatically assigned to List types in the entity, eliminating a lot of generated code in the entity.
- ToMany comes with change tracking: all changes (add/remove) are automatically applied to the DB when its hosting entity is persisted via put(). Thus, the list content is synced to the DB, e.g. their relationship status is updated and new entities are put.
- Streamlined annotations (breaking API changes):
@Generated(hash = 123) becomes @Generated(123),
@Property was removed,
@NameInDb replaces attributes in @Entity and the former @Property,
Backlinking to-many relations require @Backlink (only),
@Relation is now only used for to-one relations (and is subject to change in the next version)
V0.9.11 (beta) 2017/04/25: Various improvements
- Smarter to-one relations: if you put a new object that also has a new to-one relation object, the latter will also be put automatically.
- Getters and setters for properties are now only generated if no direct field access is possible
- JSR-305 annotations (@Nullable and others) to help the IDE find problems in your code
- @Uid(-1) will reassign IDs to simplify some migrations (docs will follow soon)
- No more getter for ToOne objects in favor of direct field access
- Quite a few internal improvements (evolved EntityInfo meta info object, etc.)
V0.9.10 (beta) 2017/04/10: Bug Fixes and minor improvements
New features and improvements
- Breaking API: Replaced “uid” attribute of @Entity and @Property with @Uid annotation
- An empty @Uid will retrieve the current UID automatically
- Some minor efficency improvements for read transactions
- Better DB resources clean up for internal thread pool
- Better compatibility with Android Gradle plugin
- Fixes for multithreaded reads of relation and index data
- Fixed compilation error in generated sources for Entities without non-ID properties
V0.9.9 (beta) 2017/03/07: Bug Fixes
- Query.forEach() to iterate efficiently over query result objects
- Various bug fixes
V0.9.8 (beta) 2017/02/22: Going Reactive
- Data observers with reactive extensions for transformations, thread scheduling, etc.
- Optional RxJava 2 library
- OR conditions for QueryBuilder allow more powerful queries
- Fixed: Changing the order of an entity’s properties could cause errors in some cases
- Fixed: Querying using relation IDs
V0.9.7 (beta) 2017/02/10
- LazyList returned by Query: another query option to defer getting actual objects until actually accessing them. This enables memory efficient iterations over large results. Also minimizes the time for a query to return. Note: LazyList cannot be combined with order specifications just yet.
- QueryBuilder and Query now support Date and boolean types directly
- QueryBuilder supports now a notIn opperator
- put() now uses entity fields directly unless they are private (can be more efficient than calling getters)
Breaking internal changes
At this early point in the beta we decided to break backward compatibility. This allowed us to make important improvements without worrying about rather complex migrations of previous versions. We believe this was a special situation and future versions will likely be backward compatible although we cannot make promises. If you intend to publish an app with ObjectBox it’s a good idea to contact us before.
- The internal data format was optimized to store data more compact. Previous database files are not compatible and should be deleted.
- We improved some details how IDs are used in the meta model. This affects the model file, which is stored in your project directory (objectbox-models/default.json). Files created by previous versions should be deleted.