Greetings! I have a conference app (lists sessions, hotel maps, etc.) from last year that I plan to enhance.
First, I am going to store the session details JSON in the backend services (as a file, not data type) instead of in the app.
ALso, I want to allow each user to select which sessions they will attend (checkbox on "all sessions" view) and also show a "my sessions" view of the selected items. Obviously, I am going to store the selections separately. My SQL background makes me want to add a data type to the backend services with columns such as userId and sessionId. I read the documentation relations and offline storage, and I am left with questions
1. Can I join the JSON and data type using the relation support?
2. Since both of these are coming from everlive, I assume that when I set backend instance offline that both will be available, and when online the user selections will synchronize (user cannot change sessions JSON). Does it make a difference how I construct the relation is order to persist changes to the users session selection when offline? That is, should the selection table be primary and relate the session list to it (or would that give me trouble to display non-selected items?) or should the session list be primary and relate the selections to it (makes sense but not sure how to save selections then...)
I have cloned the deliveries app, and I'm sure it will be helpful, but it seems a bit simpler (only one table).