I figured out the solution to the problem I was asking about below.
It was more of a beginner's question than I thought. The solution was
to add the following index to index.yaml:
- kind: assessment_item
properties:
- name: class
- name: __key__
direction: desc
The problem was that I didn't really know how to find the exception
stack traces and was assuming that they weren't being logged. In fact
exceptions are being logged. I had two versions of the application
uploaded, and there is a dropdown box in the log viewer that allows
you to select the version. I didn't know about the box and was
looking at logs for an earlier version of the application.
Eric
On Apr 12, 3:01 pm, Eric Walker <eric.wal...@gmail.com> wrote:
> Hi everyone,
>
> I have a beginner's question I wasn't able to find documentation on.
> I'd be grateful if someone could point me to a specific page or issue
> number that discusses it.
>
> I just finished debugging a simple pager that pages over aPolyModel
> subclass using the __key__ in descendingorder. It works on the
> development server but not in production, where an unspecified
> exception is thrown (nothing appears in the log). Here is the
> offending line:
>
> result = self.model.all().order('-__key__').fetch
> (self.pagesize + 1)
>
> The application works in production with the following modified
> version of the line:
>
> result = self.model.all().fetch(self.pagesize + 1)
>
> One approach I've tried as a workaround is toorderby an "added"
> timestamp property in thePolyModelbase class, which results in an
> exception as well. Another thing I've tried is to manually add the
> following index to index.yaml, which wasn't being created
> automatically by the development server (I assume it's not necessary):
>
> - kind: QuestionGroup
> properties:
> - name: __key__
> direction: desc
>
> Adding this definition didn't fix the problem either.
>
> I understand that there was a similar ordering issue that was
> addressed inhttp://code.google.com/p/googleappengine/issues/detail?id=884.
> According to a comment, the problem was fixed in 1.1.8 (I'm using
> 1.2.0).
>
> Please let me know if I've left something important out.
>
> In a different connection, the pager turned out to be pretty finicky
> to debug, as I wanted both a "next" and "back" link, and I
> unintentionally introduced a lot of off-by-one errors. Has been
> logged for a feature request for paging that I can follow? I assume
> this is something that most projects will need at some point.
>
> Many thanks in advance for any help,
> Eric
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
