Hi Jan, Based on the information you provide its hard to say if that's a good idea or not; perhaps for your problem it is the best way, maybe it is not. If you are going to run multiple queries, I would try to run them asynchronously to reduce the latency.
The idea is not necessarily without merit, Google for zig-zag merge join. You can watch the "Building scalable, complex apps on App Engine" IO talk for a nice description of it. You need to make sure you take into account how the results will be ordered when they're returned to you. You should also consider the sizes of the result sets. If you want alternate suggestions you should provide a description of the (specific) _problem_ not only the solution. ;) Robert On Tue, Feb 15, 2011 at 05:28, Jan <[email protected]> wrote: > In our company we feel obstructed by the restriction that a query may > only contain one inequality filter like startsWith. > Currently we are thinking about performing two independent startsWith > queries and combining the result inside the service method. > Do you think this is a good idea? > Does anybody have experience with such a strategy or even know a > better solution? > > Thank you very much > Jan > > -- > 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. > > -- 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.
