Florina Muntenescu
Jul 20, 2017 · 1 min read

Depends on what’s in the List.

If you have something like:

class User {
String userName;
List<Pet> pets;
}

Then you would need another table for pets. Check out how to handle database relationships here.

If you just have List<String> maybe you could concatenate that List in one String and save that as one field in your table.

)

    Florina Muntenescu

    Written by

    Android Developer Advocate @Google

    Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
    Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
    Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade