Just because its one *sql query* - doesnt its one query against the database. All the 'unions' just run each query seperately and the combine the results.
The only difference with AppEngine you need to implement the 'combine' or union in your application, rather than the database doing it for you. So while sqlite (or other SQL engines) may make it simple to implement, its not going to be able to make it *that much* more effienct that just running the queries seperatly. If you want the source to be 'consise' you could implement a function/class that does the seperate queries and combines them for you. Much like the datastore API does for 'or' queries - in the background really its a number of datastore queries. 2008/12/22 Hardi <hardi.kovam...@gmail.com>: > > Hi! > > I'm porting a php application over to App Engine and while everything > else is rather trivial, I'm having trouble converting the search > function. This is what I have as my query in php - > http://utilitybase.com/paste/10419 > It's a weighted search query for sqlite and it works very well. > > I'm having some trouble wrapping my head around datastore as it is > (there are too few examples!), but so far it seems I would have to > make several querys, and then combine the results.. nothing nowhere as > concise as that one.. :/ Or have I overlooked something? > > I appreciate all hints, thank you! > > Hardi K. > > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
