> Can someone also please tell me whether or not the index.yaml file > plays a role in running the app on localhost or not. I cannot > comprehend why the app (even the feature that needed that particular > index) was working fine on localhost if the index.yaml was malformed > and the same app breaks down for the want of an index it fails to > update. >
I don't know much about the Python environment, but I can confirm that in Java this is an issue too. The development server seems to return full sets of results for queries that won't work in production without an explicit index construction. This happened to me while filtering for equality on multiple properties (i.e. "where prop1==param1 && prop2 == param2"). The development server returned the full set of queried objects, production server returned an empty set since no index was built. Also, no index was authomatically generated in development (I don't know if this feature is available in python, too). The need for the index (and the lack of auto-generated ones) is stated somewhere in documentation (not clearly recognizable, I should say); discrepancy between production and the devserver is not. Regards Lorenzo -- 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.
