What’s new in Room (Android Dev Summit '19)

[@Gabbitt0]

Pre-package db feature was really needed, thanks for this 💯

[@tejasgandhi4370]

how to insert owner and list of pets(1 to many) in one go? To get the value you need to provide a class that is annotated with @Entity in Room. but we cant annotate PetAndOwner class.

[@swornimshah8898]

We need better room migrations helper classes

[@GakisStylianos]

I see you took the opportunity to impress everyone in the room with your puns :P

[@codinginflow]

in the *Room

[@TZCoder]

Amazing that Google still cant figure out how to properly edit a tech talk! Show the slides not the person! Or stick the person in a side window, you literally skipped some of the slides

[@aliciabeltran]

Great talk and infographics

[@yuehernkang]

Great talk !

[@someman7]

Is it me or are slides riddled with errors? How is the query always "SELECT * FROM Owner"? Or is there code missing that would transform those objects by accessing a member of the object? If so, don't I now have a 1+N query problem? I would want to see a JOIN should be in there somewhere but I don't. If it is opaque to me, then my concern is that it runs when I don't need it. Anyone have any insight into this? I never worked with Room.

[@kheavmady8780]

Good, but how to implement with Cipher?

[@ildarka90]

Omg these puns😂 Very interesting talk tho, thank you!

[@owaistnt]

Features of Rooms are impressive but this talk had some room for Energy. Though 16 min but felt like its long.

[@Rajmanov]

Super nice talk Daniel!

[@santiagoburroni2224]

really interesting stuff, i've been using the non stable builds of 2.2.0 and they came just in time for new features needed at work. Also, this is a shot in the dark, but: i have a "SELECT * from table_a, table_b, table_c..." for 8 different tables. the return type is a class with 8 Embedded classes, each having an embedded room entity and a 1:M Relation to a list of Entity. this return item is always null, except when all 8 tables are populated, in which case it returns the item with the subitems with the sublists. i have been working on a patchy workaround in the meantime, but i'm really curious as to why this behaviour is happening. is the query somehow worded wrong? is this beyond the capability of room, somehow, and i should query each of the 8 embedded classes individually and then create the return type myself? also, on that note, what would be the best approach to merge 8 livedatas into a new one, using a mediatorlivedata, and avoiding unnecessary data emission callbacks? thank you all!

[@aba.m1]

Maybe you should try shooting in stackoverflow

[@dewiangrainidewisartikams6726]

Thanks yeah me on here summit tgk on 2019

[@TheDnaitsirc]

Expand projections... So specifying columns is something new ..

[@itscooldawgdonteventrip]

the Room jokes are cool :)

[@manishkhabri7327]

Android dev summits are the most boring. Unity summits are the coolest. :P