Word of the day: “Transmogrify”
“to transform, especially in a surprising or magical manner.”
Mark draws a great comparison between Room and Retrofit as they both use annotation processing, and describe either a URL path, or a DB query. The @Query annotation in Room, is similar to the path in Retrofit that is provided to @GET, @POST, etc.
Parameters can be sent with the syntax :postalCodes. You can pass parameters into a query this way:
@Query(“SELECT * FROM Customer WHERE postalCode IN (:postalCodes)”)
List<Customer> findCustomersInPostalCodes(String… postalCodes)
Cool DB Testing Tip for Android Instrumentation Tests: In-memory databases work the same way that SQLite databases do that are saved to the disk. In-memory database are great for instrumentation tests because they are fast, and when you are done with it, it’s gone from memory, and doesn’t persist to disk. It’s not recommended to use in-memory databases in true client apps however.
Types used in Room need a @TypeConverter. You can specify the type converters to be used in the following way:
Caveats about relations:
You can use @ForeignKey on a child, but… <OMG head explosion />. Foreign keys are there, but there aren’t any magical methods generated to retrieve a child. You can just get an ID for the child, and then have to re-query for that. You can specify cascading deletes however which is useful.
Room Migrations – Create instances of Migration – A little more sane than just plain SQLite.
Note about SQLCipher – It was last updated in 2009, and the APIs are really hard (if not impossible) to integrate with Room.
LiveData – Room works really well with Rx programming. 🙂
Predictions: We will go through a lot of iterations of the APIs as kinks are worked out and things stabilized. The guess is that a final version would be available around Google I/O 2018.
Check out Mark Murphy on the internet: