Hi, Marizia. I'm sorry to cross the post.
I understand this issue is fixed. But I think that the data that put while the issue is remaining are under the influence of this issue. So the way to reccover the data is to register as new entity and to delete old one. Is it correct? Thanks. On 12月17日, 午前4:04, paptimus <[email protected]> wrote: > Hi, Marzia. > > > > Also, have you tried adding this index to your index.yaml and uploading it > > > with your application: > > > > - kind: Ownership > > > properties: > > > - name: user > > > - name: deleted > > > - name: created_on > > > direction: desc > > I added and uploaded this index according as your advice. > But this problem is not remaining. > > So I vacuumed the below index which is generated by sdk and previously > created. > > - kind: Ownership > properties: > - name: deleted > - name: user > - name: created_on > direction: desc > > But the situation is the same as before. > > Thanks. > > On 12月16日, 午前11:52, paptimus <[email protected]> wrote: > > > Hi, Marzia. Thank you for your reply. > > > It is missing. > > For example, I run this query: > > > query = models.Ownership.all().filter('user =', > > [email protected]),filter('deleted =',False).order('- > > created_on').fetch(0, 20) > > > These lists are my expecting/getting result. > > The getting result contains no 'NG' data but folowing 3 data. > > > expecting: > > 2008-12-12 10:25:23.397434 > > 2008-12-09 18:04:23.439058 > > 2008-12-03 15:22:46.754546 > > 2008-12-03 15:22:45.251281 > > 2008-12-03 15:22:42.594933 > > 2008-12-03 15:22:41.149333 > > 2008-12-03 15:22:39.559995 > > 2008-12-03 15:22:38.116000 > > 2008-12-03 15:22:36.511006 > > 2008-12-03 15:22:35.117080 > > 2008-12-03 15:22:33.679363 > > 2008-12-03 15:22:32.119234 > > 2008-12-03 15:22:30.461840 > > 2008-12-03 15:22:28.936849 > > 2008-12-03 15:22:27.518304 > > 2008-12-03 15:22:26.039718 > > 2008-12-03 15:22:24.665877NG > > 2008-12-03 15:22:23.188243 > > 2008-12-03 15:22:21.681791NG > > 2008-12-03 15:22:20.245579NG > > > getting: > > 2008-12-12 10:25:23.397434 > > 2008-12-09 18:04:23.439058 > > 2008-12-03 15:22:46.754546 > > 2008-12-03 15:22:45.251281 > > 2008-12-03 15:22:42.594933 > > 2008-12-03 15:22:41.149333 > > 2008-12-03 15:22:39.559995 > > 2008-12-03 15:22:38.116000 > > 2008-12-03 15:22:36.511006 > > 2008-12-03 15:22:35.117080 > > 2008-12-03 15:22:33.679363 > > 2008-12-03 15:22:32.119234 > > 2008-12-03 15:22:30.461840 > > 2008-12-03 15:22:28.936849 > > 2008-12-03 15:22:27.518304 > > 2008-12-03 15:22:26.039718 > > 2008-12-03 15:22:23.188243 > > 2008-12-03 15:22:18.783426 > > 2008-12-03 15:22:17.303290 > > 2008-12-03 15:22:13.102364 > > > Thanks. > > > On 12月16日, 午前5:18, Marzia Niccolai <[email protected]> wrote: > > > > Hi, > > > > Thanks for the report, but I'm not sure I understand how exactly your > > > query > > > is having an issue. > > > > Can you elaborate on this statement: "The result set is ordered by > > > '-created_on', but it is not sequential." What data are you getting? What > > > data are you expecting? Is it misordered or missing? > > > > Also, have you tried adding this index to your index.yaml and uploading it > > > with your application: > > > > - kind: Ownership > > > properties: > > > - name: user > > > - name: deleted > > > - name: created_on > > > direction: desc > > > > Thanks, > > > Marzia > > > > On Mon, Dec 15, 2008 at 11:05 AM, paptimus <[email protected]> wrote: > > > > > I get an additional information. > > > > > I vacuumed the problem index and rebuilt the same index. > > > > The number of result set before vacuum_index is not same as one of > > > > after that. > > > > Obviously, query is same. > > > > > So I think my app get into this situation while rebuilding index. > > > > I hope gae team checks my app's index. > > > > My app id is 'book-case-2' and kind is 'Ownership'. > > > > > Thanks. > > > > > On 12月16日, 午前1:23, "koji matsui" <[email protected]> wrote: > > > > > Hi, djidjadji, thanks for your comment. > > > > > > I tried both query as below: > > > > > > query = models.Ownership.all().filter('user', user),filter('deleted', > > > > > False).order('-created_on').fetch(offset, amount) > > > > > query = models.Ownership.all().filter('user =', user),filter('deleted > > > > > =', False).order('-created_on').fetch(offset, amount) > > > > > > But the definition of index sdk generates is exactly the same. > > > > > And lack of data in result set is the same. > > > > > > So, I think this problem happens when server creates the index. > > > > > > Thanks. > > > > > > 2008/12/15 djidjadji <[email protected]>: > > > > > > > A snippet from the manual > > > > > > ============== > > > > > > filter(property_operator, value) > > > > > > > Adds a property condition filter to the query. Only entities with > > > > > > properties that meet all of the conditions will be returned by the > > > > > > query. > > > > > > > Arguments: > > > > > > > property_operator > > > > > > A string containing the property name and a comparison > > > > > > operator. The name and the operator must be separated by a space, as > > > > > > in: age > The following comparison operators are supported: < <= = > > > > > > >= > > > > > >> (The not-equal (!=) and IN operators are not supported.) > > > > > > ============== > > > > > > > You forget the "comparison operator" in your filter statements. > > > > > > > 2008/12/13 paptimus <[email protected]>: > > > > > > >> query = models.Ownership.all().filter('user', > > > > > >> user),filter('deleted', > > > > > >> False).order('-created_on').fetch(offset, amount) > > > > > > -- > > > > > ----------------- > > > > > koji matsui > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
