Hi everyone- This is my first post after doing everything in my power to search for the answer in this forum and also in the GAE literature. I don't have a lot of database experience, as in this case I'm tinkering with GAE for my business (which is in the mechanical engineering world).
I'm trying to clarify what the query limitations mean, if there are workarounds, and to what extent the community thinks queries will be updated to be more powerful in the future. The best in-depth discussion that I could find was posted this past January. http://code.google.com/appengine/forum/python-forum.html?place=topic%2Fgoogle-appengine-python%2FQMgIY9CRLT0%2Fdiscussion Just to give people a sense of why I'm asking. One very popular search that I have to make (that I think an App could seriously boost productivity) may involve multiple inequality statements. I've read about these limitations in GAE. Not knowing a lot about database queries in general, and not wanting to give up on my concept, I thought that maybe this is not such a terrible limitation if I am able to filter the results of one inequality query with another inequality query. I guess you could call this a nested query. For example, let's say you wanted to understand when a variable x was below a certain threshold, AND the variable Y was greater than another threshold AND variable Y was less then a third threshold. Could I search the datastore with three different queries, the first query returning all instances where the variable X is below the threshold I seek, then run a second query where I filter for variable Y above my second threshold, and then run a third query? Is GAE really trying to limit or prevent this sort of query in the first place and I should just walk away now from trying to use GAE, or am I just taking the wrong approach to this entirely? >From what I've read it seems like GAE is really suited to simpler queries that are designed for instantaneous feedback on potentially real-time data To some extent if my software is really successful, I could see a need for this too. But I do want to have some persistent data storage, that I can call upon and query that may be more of a traditional database. What are my options and do people in the community see upcoming changes to the datastore that address these questions? PS-thanks for taking such a newbie question. -- 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.
