Thanks for the sample. As for querying sub elements, if I understand you correctly, you are saying that sub elements are treated no differently than their parent elements. In other words, Google Base's query engine sees all elements as one big flat index. You have to wonder then what the purpose is of having sub elements if you can't query for them. In a practical application, I can imagine that there would be times that you would want to query for a parent who has a sub element of some type containing some value. It appears that sub elements are only there for visual purposes. While it's true that I can read back the pure xml and write my own API to parse through the parent/child elements, that will probably result in getting a lot of unnecessary data back from Google Server in order to locate a sub element. It would be nice if the query engine allowed for a search for a sub element based upon a parent element and any some attribute type and value of the sub element.
-- You received this message because you are subscribed to the Google Groups "Google Base Data API" group. To post to this group, send email to google-base-data-...@googlegroups.com. To unsubscribe from this group, send email to google-base-data-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-base-data-api?hl=en.
