Yes, you are correct, Tim. I was misreading the error. The error was an implicit query:
for x in self.things: where self.things, behind the scenes is, of course, a query. My overall point though is the nature of the messages. Imagine this from a compiler: line 13: Uninititalized variables not permitted. vs. line 13: Uninitialized variable: x Error messages shouldn't be general rules of the platform, they should point to specific parts of the code that break those rules. On Dec 4, 3:45 pm, Tim Hoffman <[email protected]> wrote: > HI > > On Dec 5, 7:24 am, laboo <[email protected]> wrote: > > > Why doesn't this error message... > > > "Only ancestor queries are allowed inside a transaction." > > > ...look something like this... > > > "Only ancestor queries are allowed inside a transaction. Entity X is > > not an ancestor of Entity Y" > > I think you are misreading the error. Its not EntityX is not an > ancestor > it says you are doing a query, that doesn't have > ancestor(some_ancestor) in it. > > A closer look at your code will reveal the problem. > > More docs are nice, but on the whole I don't agree with your laziness > sentiments. > > T -- 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.
