... > > I started looking at the person object and all its fields and > relationships.... to share some of the things correctly, like jobs -> > organizations -> addresses, or the potentially wide range of properties > (array of likes).... > > The complexity of the full model soon made me go and look at ORM of some > form.
Yep, I hear ya. I did the same thing. I found the relationships between the people and the other objects somewhat complex - but not insurmountable. A lot of it depends on how the data is extracted from the DB.. In this manner, I just did a manual mapping mainly because I know how it's sometimes hard to deal with resultant code when you use automated mapping..especially in complex cases. For my tutorial, I just opted for a simple manual approach for starters. It was actually kind of fun doing a manual relational mapping. It may not be perfect, but it's a start. :-) > > >> Were you thinking of doing more work in this area ? Do you want to >>> >> collaborate ? >> >> Sure, would be happy to. >> > > If you get a chance, can you take a quick look at the ORM version at the > link, and see if it makes any sense. I would be fine to focus on either > approach, the main thing in my mind is to get a reasonably solid RI that can > actually be used in small scale production for those that want to build > something off shindig, (small scale probably == < 1M users ?), Yep, I definitely agree. Which "link" are you referring to? -Chris > > > Ian > > -- Chris Schalk, Google Developer Advocate
