Room 2.5.0-alpha02

2.5.0-alpha02
Added 2
  • New room-paging-rxjava2, room-paging-rxjava3 and room-paging-guava artifacts for support in Room Paging
  • Added APIs for providing key and value table names for disambiguation in @MapInfo
Changed 1
  • All of room-runtime has been converted from Java to Kotlin
Fixed 2
  • Fixed a source compatibility issue to re-allow @Ignore in property getters
  • Room now attempts to resolve ambiguous columns in multimap queries using a duplicate column resolution heuristic, so JOINs with same-name tables map correctly to a result data object

From Room

New Features New room-paging artifacts room-paging-rxjava2, room-paging-rxjava3 and room-paging-guavahave been added for support in Room Paging.( 41a1d4, b/203666906),( eb6098, b/203666906),( 1b9ae4, b/203666906) API Changes All of room-runtime has been converted from Java to Kotlin. ( If2069, b/206859668),( Ie4b55, b/206859668), ( I697ee, b/206859668), ( I96c25, b/206859668) Note: You may encounter source incompatibility issues due to the library conversion to Kotlin. If your code was in Kotlin and calling the old version of Room, the new version will need to handle these cases. For example, a known source incompatible change is that in InvalidationTracker you will now need to declare onInvalidate() in Observer to have a param of type Set and not MutableSet. Added APIs for providing key and value tables names for disambiguation in @MapInfo ( Icc4b5) Fix a source compatibility issue to re-allow @Ignore in property getters. ( Ifc2fb) Bug Fixes Duplicate column resolution heuristic algorithm. Room will now attempt to resolve ambiguous columns in a multimap query. This allows for JOINs with tables containing same-name tables to be correctly mapped to a result data object. ( I4b444, b/201306012, b/212279118)

View original

Upgraded? How did it go?

Discussion