Can you give a more concrete example of the two cases (maybe provide some code)? I'm trying to figure out what you're doing so I can list off tradeoffs that I see.
-- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Sat, Nov 26, 2011 at 4:17 AM, Ice13ill <andrei.fifi...@gmail.com> wrote: > Hi, I was wandering which of the following data models are ore > efficient. Let's say i have three fields form my entity: name (a > simple fileld), some_property (simple field), list_of_properties (a > list of properites). > - case 1. index: ^name, ^some_propery, ^list_of_properties. > - case 2. index: ^name, ^list_of_properties (but all the information > that relates to the filed "some_property" is stored in > "list_of_properties" as a string: some_property=a_property_value) > > What are the advantages/disadvantages of each case (performance, > metadata generated / size of all data, etc) > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
