Well let's say I have an Entity with the following fields: - String name - String type - List<String> properties
The purpose is to search these entities (for example: the user inputs the search words to be matched against "properties" field and the "name" and "type" are matched according to some other settings/ options) So let's say I can use this index: name^ , type^ , properties^. But another option would be to remove the "type" field and insert the same information in the "properties" list filed as "type=some_value_of_type" so and I could use this index: name^ , properties^. I believe that any of this is a solution for searching my Entities (is it possible that i'm missing something ?), but i was wandering what are the differences (advantages/disadvantages) regarding query performance, quotas etc. On Nov 29, 10:57 pm, "Brandon Wirtz" <[email protected]> wrote: > I think you are doing someone's home work :-) > > From: [email protected] > [mailto:[email protected]] On Behalf Of Ikai Lan (Google) > Sent: Tuesday, November 29, 2011 10:58 AM > To: [email protected] > Subject: Re: [google-appengine] Question about indexing of properties > > 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 <http://plus.ikailan.com/> | twitter.com/ikai > > On Sat, Nov 26, 2011 at 4:17 AM, Ice13ill <[email protected]> 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 [email protected]. > To unsubscribe from this group, send email to > [email protected] > <mailto:google-appengine%[email protected]> . > For more options, visit this group > athttp://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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
