To clarify my post with some examples:
select * from Transaction where ancestor is
key('ahBoaWdodm9sdW1lc2VsbGVycg8LEgdBY2NvdW50GNrrGAw') order by
dateReceived DESC
returns Transactions that have dateReceived all NULL
select * from Transaction order by dateReceived DESC
return Transactions that have dateReceived NOT NULL, but there are
Transactions missing that show if I issue the first GQL but omit the
'order by dateReceived DESC'
Here are my index defs
<datastore-index kind="Transaction" ancestor="true">
<property name="dateReceived" direction="desc"/>
</datastore-index>
<datastore-index kind="Transaction" ancestor="true">
<property name="dateReceived" direction="asc"/>
</datastore-index>
On Apr 26, 1:06 pm, John Wheeler <[email protected]> wrote:
> I have a table called Transaction and a property on that table called
> dateReceived. Some entries have dateReceived with a datetime, and some
> are null. When I try to ORDER BY dateReceived either ASC or DESC (I
> have indicies for both), all I get back are the NULL columns. This is
> what happends when I use one of these indexes, which also includes
> ancestor.
>
> If I use the built in dateReceived index, I am getting back
> Transactions sorted chronologically by date, but not all of them are
> coming through. Some of the most recent entries that are returned when
> I do an *ancestor query only* are not coming back, so I thought it
> might be an ancestor issue, maybe I was saving some entities without
> their parent key, but in the datastore view, i do see they all have
> parent keys.
>
> This is very frustrating and I wish I understood datastore indexes
> better. I would be grateful to anyone who can shed some light
--
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.
